To simplify diagnosis, the UPIC carrier system keeps a log file. A UTM error message is written to this file if the UTM application terminates a conversation abnormally. The log file is opened only for writing the error message (append mode) and is then closed again.
The file can be read using any editor.
Windows systems
The log file has the name UPICLtid.UPL, where tid is the thread ID. You can define which directory the log file will be stored in by means of the environment variable UPICLOG (see section “Runtime environment, environment variables on Windows systems”).
If the UPICLOG environment variable is not set, the following are interpreted in the order shown:
the TEMP variable
the TMP variable
If a corresponding entry is found, the directory specified there is taken. If nothing is found, the file is stored in the %TEMP% directory. This directory must exist and the CPI-C program must have write permission for this directory because otherwise log files will be lost.
Unix and Linux systems
The name of the log file is UPICLpid, where pid is the process ID. You use the UPICLOG shell variable to define the directory in which the log file is stored. If this shell variable is not set, the file is stored in the /usr/tmp directory.
BS2000 systems
The name of the logging file is UPICLtsn, where tsn is the TSN of the BS2000 task.
You specify the prefix for the logging file using the job variable with the link name UPICLOG (see section “Runtime environment, linking, starting”).
If UPICLOG is not set, the system writes to the following logging file:
##.usr.tmp.UPICLtsn
If a UPIC process is re started on the BS2000 system without performing a LOGOFF/LOGON, the TSN tsn is retained. This means that the logging file is overwritten!