If an error occurs in the attempt to write a UTM message in the SYSLOG, openUTM outputs UTM message K043, which contains a DMS error code. This error code indicates the reason for the error.
The subsequent behavior of openUTM depends on whether the SYSLOG is maintained as a simple file or as an FGG.
The SYSLOG is maintained as a simple file:
After UTM message K043 is output, the application is terminated with reason SLOG09.
The SYSLOG is maintained as an FGG:
When an error occurs, openUTM attempts to switch to the next file generation. openUTM also switches generations if size monitoring is deactivated or not generated. openUTM does not switch generations if size monitoring is suspended as a result of a previous switching error.
If the switching attempt fails, the application is terminated with reason SLOG09.
If openUTM can successfully switch to the next file generation, openUTM makes another attempt to write the UTM message in the SYSLOG. If an error occurs in this attempt, the application is terminated with SLOG09. If no errors occur, the application continues running and openUTM logs the UTM messages in the new SYSLOG file generation.