Change SERSLOG file
Component: | BS2000 |
Functional area: | Error logging |
Domain: | ERROR-LOGGING |
Privileges: | TSOS |
Routing code: | A |
Function
The CHANGE-SERSLOG-FILE command is executed only if software error logging is active.
The command closes the current SERSLOG file for logging relevant software errors ($TSOS.SYS.SERSLOG.yyyy-mm-dd.xxx.nn) and opens a new one (with nn+1). The switchable logging procedure SERSLOG, which up to the time of command input has entered a record in the old file for each relevant software error, from now on will enter the records in the new file. The records automatically include the time, caller and further identifiers.
The information collected in the closed file can still be evaluated during the system session.
If the new SERSLOG file cannot be opened due to a DMS error, a message to that effect is issued at the operator terminal. In this case the old SERSLOG file remains the current file. If another CHANGE-SERSLOG-FILE command is issued, an attempt is made to open the next-but-one SERSLOG file. If the attempt succeeds, the number nn in the file name (see above) is incremented by 2 in order to mark the error in the sequence of files.
Format
CHANGE-SERSLOG-FILE |
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | No error | |
2 | 0 | NER0000 | Internal error |
32 | CMD0221 | System error | |
32 | NER0000 | Internal error | |
64 | NER1070 | Task break during processing | |
64 | NER1000 | No authorization for command | |
64 | NER1040 | DMS error | |
128 | NER0010 | A SERSLOG command is already being processed | |
129 | NER1020 | SERSLOG function is not active |
Example
/show-serslog
% NER1060 SERSLOG ACTIVE. FILE : ':SBZ7:$TSOS.SYS.SERSLOG.2017-01-27.006.01'
/change-serslog-file/show-serslog
% NER1060 SERSLOG ACTIVE. FILE : ':SBZ7:$TSOS.SYS.SERSLOG.2017-01-27.006.02'