The software error logging function SERSLOG has been provided to facilitate the diagnosis of BS2000 errors. BS2000 error information can be written to the SERSLOG file by various routines.
During startup, the SERSLOG file is opened and error logging activated. The name of the SERSLOG file has the following format:
SYS.SERSLOG.yyyy-mm-dd.xxx.nn
yyyy-mm-dd | Date on which the file was opened |
The SERSLOG file is not write-protected.
During shutdown, the SERSLOG file is closed and error logging terminated.
The current (or most recent) SERSLOG file is included in the SLED dump.
Error logging can only be controlled by the operator and systems support, who can switch the SERSLOG file and activate or deactivate error logging.
When nn is greater than 99, the counter is reset to 01, thus overwriting the first SERSLOG file if the date and the session number are the same.
Command | Meaning |
CHANGE-SERSLOG-FILE | Close the current SERSLOG file and a open new file |
SHOW-SERSLOG-STATUS | Request information on the state of SERSLOG and the name of the logging file |
START-SERSLOG | Activate the SERSLOG function |
STOP-SERSLOG | Terminate the SERSLOG function |
Automatic monitoring of critical system statuses which are reflected in SERSLOG events is possible with ASE. For details, see the chapter "ASE Auxiliary SERSLOG Extensions".