System log file SYSLOG

openUTM logs 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 BS2000 Systems” for information on message destinations).

The system log file SYSLOG can be used for actively monitoring the application run or for subsequent checking. The SYSLOG file provides important information, particularly for diagnostic purposes.

You must provide a SYSLOG file for each UTM application. If you have not assigned a SYSLOG file to a UTM application before the start, the application start will be terminated.

The system log file SYSLOG can be created as:

• a simple SYSLOG file

• a file generation group SYSLOG-FGG

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. If all tasks of the application have closed the old SYSLOG file, then this file generation is available to you for your use.

• 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 <filename>

• Message K138 at the end of the application:

  K138 SYSLOG file <filename> closed

• Message K137 after switching to another file generation:

  K137 SYSLOG switched to file <filename>