Automatic size monitoring can only be used for FGGs. If you create the SYSLOG file as a simple file and generate automatic size monitoring, then openUTM terminates the start of the application with start error code 58.
Automatic size monitoring can be set in two ways:
in the UTM generation using the KDCDEF statement MAX ...,SYSLOG-SIZE=size
while the application is running, using the administration command
KDCSLOG [SWITCH,]SIZE=size or on the administration program interface with the operation code KC_SYSLOG and subopcode KC_CHANGE_SIZE (see the openUTM manual “Administering Applications”)
In both cases, you must set a value > 0 for size.
When size monitoring is switched on, openUTM does not write any UTM message to the SYSLOG file before checking whether writing this UTM message would exceed the agreed maximum size of the file generation (size * size of a UTM page). If this is the case, an attempt is made to switch to the next file generation. If successful, openUTM outputs UTM message K137.
If the attempt to switch generations results in an error, openUTM continues to work with the old file generation in which data was logged before the switching attempt was made. openUTM writes UTM message K139 to SYSOUT and to the administrator console. In addition, UTM message K043 is output for all DMS errors. This contains a DMS error code indicating the reason for the switching error.
To ensure that openUTM does not unsuccessfully attempt to switch to the next file generation for each subsequent UTM message with the destination SYSLOG, automatic size monitoring is deactivated after this type of switching error.
After the administrator has found and eliminated the cause of the switching error, automatic size monitoring can be reactivated using the KDCSLOG SWITCH command, for example. When KDCSLOG SWITCH is issued, openUTM is forced to begin a new switching attempt. If this attempt runs without errors, the previously deactivated size monitoring function is automatically reactivated.
openUTM guarantees that no more UTM messages are written to the old file generation following the switch. However, this does not mean that the old file generation is freely available immediately. First, all tasks of the application must close this file generation. This may take longer if tasks are using user program units for a very long time. When a file generation is closed by the last task, openUTM outputs UTM message K138.
The output of the administration command KDCSLOG INFO indicates which file generations are closed (LOWEST-OPEN-GEN).
openUTM does not change the FGG base set by the user at the start of the application. This means that file generations are not lost unintentionally even if the FGG option OVERFLOW-OPTION = KEEP-GENERATION is set.