Software error logging in BS2000 consists of two parts: saving the data on all software errors encountered, and editing this data. Data relevant to the software errors encountered is saved with the aid of the operating system function SERSLOG. Selected data relating to each software error is written into a special file, the SERSLOG file. In order to avoid impairing system performance, this data is not subjected to further editing at this point. It can be edited and evaluated later with the aid of the utility routine ELFE (Error Log File Evaluation, see "ELFE Edit and evaluate the SERSLOG file").
The following overview contains all the commands available to the operator and the system administrator for controlling software error logging. The commands are described in detail in the “Commands” manual [8].
Commands | Function |
CHANGE-SERSLOG-FILE | Closes the current SERSLOG file and opens a new one. |
SHOW-SERSLOG-STATUS | Shows the status of error logging and the name of the SERSLOG file. |
START-SERSLOG | Starts software error logging and opens a SERSLOG file. |
STOP-SERSLOG | Closes the SERSLOG file. |
Table 19: Overview of SERSLOG commands
SERSLOG file
A SERSLOG file is made up of individual records written by SERLSOG when an error occurs. Each record comprises the ELSN (Error Log Sequence Number), the designation of the error event type (“rectype”), the TSN, the TID, the name of the module which caused the entry, the time of the error event and data from the environment of the software error.
The SERSLOG file is opened during system startup when software error logging is activated. The name of the SERSLOG file has the following format:
SYS.SERSLOG.yyyy-mm-dd.xxx.nn bzw. SYS.SERSLOG.yy.mm.dd.xxx.nn (depending on the setting for the system parameter FMTYFNLH – for more details see the manual “Introduction to System Administration” [6]).
where:
| is the date on which the file is opened. is the number of the associated session. is the sequence number of the SERSLOG file (01 to 99, always begins with 01 at startup time). If nn becomes greater than 99, the counter is reset to 01; this causes the first SERSLOG file to be overwritten. |
The SERSLOG file is not write-protected.
When the system run is terminated, the SERSLOG file is closed and software error logging is terminated. The current SERSLOG file is included in the SLED output.
Only the operator and the system administrator can activate (START-SERSLOG) or deactivate (STOP-SERSLOG) software error logging or switch the SERSLOG file (CHANGE-SERSLOG-FILE). The SHOW-SERSLOG-STATUS command allows you to request information on software error logging.