No monitoring data is output in the STATUS TABLE.
Output comprises two parts. The first part provides the user with information on which SM2 tasks exist and on the status of the subsystems used by SM2. The line containing “MISSED RECORDS” is only output if unwritten records exist.
The second part outputs as many of the most recent trace entries as can be accommodated on one screen.
The SHOW-SM2-STATUS statement is used to request the output of the STATUS TABLE. This statement is only available to privileged users in the administration part.
HOST0001 SM2 STATUS TABLE <date> <time>
TASK / SS START TIME STATUS END TIME
GATHERER <date> <time> RUNNING
WRITE-TASK <date> <time> ENDED <date> <time>
USER-WRITE-TASK <date> <time> RUNNING
BCAM-SM2 <date> <time> IN USE
UTM-SM2 <date> <time> UNAVAIL
SHC-OSD <date> <time> IN USE
LAST TRACED EVENTS
CUR# TIME TSN REASON TYPE MODUL ID CODE
8 15:12:03 SM2U CREATE TASK UDM 0000 00000000
7 15:08:53 SM2G UTM-NLD SS UTM 0010 00400008
6 15:08:39 SM2G BCM-STA SS DSSM 0000 00000000
5 15:07:58 SM2G STS-STA SS STS 00A0 00000000
4 10:21:04 SM2W TERM TASK GDM 1F54 00000000
3 10:19:53 SM2W CREATE TASK GDM 016E 00000000
2 10:19:22 SM2G CREATE TASK GAT4 0000 00000000
1 10:19:22 038E SM2-STA SS 84S 0000 00000000
Monitoring information
TASK / SS | Name of the task or subsystem |
START TIME | Date (in ISO4 format) and time at which the task or subsystem was created |
STATUS | Status of the task or subsystem |
Meanings of the entries for tasks: | |
RUNNING | Task running normally |
ENDED | Task terminated normally |
ABENDED | Task terminated abnormally |
Meanings of the entries for subsystems: | |
IN USE | SM2 is working with the subsystem |
UNAVAIL | SM2 requires data from the subsystem, but the subsystem is not running |
UNUSED | SM2 is no longer working with the subsystem (of its own accord) |
ABENDED | SM2 is no longer working with the subsystem because the subsystem is no longer running |
STOPPED | SM2 has unloaded the subsystem |
END TIME | Date (in ISO4 format) and time at which the task was terminated or at which the subsystem stopped being used |
MISSED RECORDS | This information is omitted if SUM = 0. |
SUM | Total number of unwritten records (in the current SM2 output file) |
LAST INTERVAL | Unwritten records in the last cycle |
MISSED EVENTS IN LAST COSMOS SESSION | |
Number of missed events during the last COSMOS session | |
LAST TRACED EVENTS | |
CUR# | Number of the trace entry (descending) |
TIME | Time of the trace entry |
TSN | TSN of the task in which a trace entry was written |
The SM2 system tasks have the following default TSNs: | |
GATHERER | SM2G |
WRITE-TASK | SM2W |
USER-WRITE-TASK | SM2U |
REASON | Reason for the trace entry. In many cases (with TYPE=S-ER) this is the name of the system function which reported an error. |
CREATE | Creation of task |
TERM | Termination of task |
Subsystem-STA | Start of subsystem use |
Subsystem-STO | End of subsystem use |
Subsystem-NLD | Subsystem not loaded |
TYPE | |
I-ER | Internal error (internal error during execution of SM2) |
S-ER | System error (error calling a BS2000 system function) |
TASK | Task event (start/end/crash of an SM2 task) |
SS | Subsystem event (start/end of subsystem use by SM2) |
MODUL | Abbreviated name of the SM2 module writing the trace entry (without “NPS”, “NPFS”) |
ID | Identifies the location at which the error occurred. In many cases this is the offset within the module. If the error is unique within the module, this field contains no entry. |
CODE | Return code of the system function called (for TYPE=S-ER) or additional information (for TYPE=I-ER) or zero |