openUTM logs all events from the application run in the system log file SYSLOG (SYSTEM LOGGING), i.e. openUTM writes all UTM messages with the UTM message destination SYSLOG to this file (see the openUTM manual “Messages, Debugging and Diagnostics on Unix, Linux and Windows Systems” for information on message destinations).
The system log file SYSLOG can be used for actively monitoring the application run or for subsequent checking. SYSLOG provides important information, particularly for diagnostic purposes.
The SYSSLOG of the application is always contained in the filebase directory, where filebase is the directory under which the application is installed (base name of KDCFILE; defined in MAX KDCFILE).
openUTM provides two options for maintaining a SYSLOG:
as a simple file SYSLOG in the filebase base directory
as a file generation group SYSLOG in the filebase base directory
A SYSLOG-FGG has the following advantages over a simple SYSLOG file:
You can switch to the next file generation during live operation (switchable SYSLOG file). You can administer the SYSLOG with the KDCSLOG administration command, for example. See the openUTM manual “Administering Applications” for more information. openUTM closes the previously used file generation when a switch is made.
You can set automatic size monitoring for the SYSLOG. This means that you can generate or specify via the administration a threshold value for the size of the individual file generations of the SYSLOG-FGG. When this threshold is reached, openUTM automatically switches to the next file generation of the FGG. Size monitoring can be enabled and disabled while the application is running.
Messages from openUTM
openUTM outputs the following messages regarding the SYSLOG:
Message K136 at the start of the application:
K136 (First) SYSLOG file is &FNAMMessage K138 at the end of the application:
K138 SYSLOG file &FNAM closedMessage K137 after switching to another file generation:
K137 SYSLOG switched to file &FNAM