An example of what goes in the temporary path are trace files.
The temporary path evaluation has Linux and IBM i differences. First TPTH, ROOT, PROC, FORM, MODE and all the trace x_run parameters (e.g. ITRO) are evaluated.
This is how the temporary path directory is resolved:
1. TPTH x_run parameter, in any of the accepted locations for an x_run parameter.
2. TEMP environment variable.
3. TMP environment variable.
4. <sysdir> directory
5. It should never get here, but if it does, a Fatal error occurs. As the temporary directory is required to write trace and error files, interactive jobs will show a message box and server jobs will output a message to STDOUT. On Windows the Listener can be run as a process rather than as a service to see these messages (lcolist –sstop; lcolist –c –d –x)
In the above list <sysdir> is the path of the x_lansa directory. For example, on Windows it could be c:\program files\lansa\x_win95\x_lansa. On Linux and IBM i it could be /home/LANSA_devpgmlib/x_lansa.
Enclosing double quotes and all trailing path separators and blanks are stripped before validating the directory.
If the directory does not exist then an attempt will be made to create it. If it fails then the next step is used.
The typical value for a temporary directory on Windows will be %TEMP% (typing that into Windows Explorer will take you to the directory). Note that server jobs typically use the user Local Server. Its %TEMP% value is not the logged on user's! For example, it may be c:\windows\temp. Process Monitor can be used on lcolist.exe to see the value of its TEMP environment variable.
The typical value for temporary directory on Linux and IBM i will be: /lansa_devpgmlib/x_lansa/tmp
When the temporary directory is resolved, it is output to STDOUT.
The log directory contains x_err.log and export.log.
On Linux and IBM i, the log directory follows the same path as the temporary directory on Windows. That is:
1. LOGDIR environment variable
2. <sysdir>/log directory, if it exists or if it can be created