Reading and Interpreting S-Series System Log Files

$SYSTEM.ZSERVICE.ZCT08153 A catalog containing a table used by the
TSM client software for converting alarm
and IR binary values into text strings.
$SYSTEM.ZSERVICE.ZCT08458 A catalog used by the resource access
layer (RAL) of TSM when reporting errors.
It contains a table for converting binary
values into text strings.
$SYSTEM.ZSERVICE.ZZAAnnnn OSM alarm files.
$SYSTEM.ZSERVICE.ZZALnnnn TSM server alarm files.
$SYSTEM.ZSERVICE.ZZDCnnnn TSM inventory (snapshot) files.
$SYSTEM.ZSERVICE.ZZPSnnnn Files containing processor scan strings.
Used by OSM.
$SYSTEM.ZSERVICE.ZZSNnnnn A text file containing a snapshot of the
system at a particular time. Used by OSM.
$SYSTEM.ZSERVICE.ZZSSnnnn Files containing processor scan strings.
Used by TSM.
$SYSTEM.ZSERVICE.ZTRC* Text files containing user trace logs. Used
by OSM.
$SYSTEM.ZSERVICE.ZTRC File containing a pointer to the current
user trace log. Used by OSM.
EMS Event Logs
$SYSTEM.ZLOGnn.ZZEVnnnn ($0)
Customer applications and some NonStop S-series server subsystems write
EMS event messages to the EMS collector process $0 (the operator log).
The $0 log is normally located on the $system.zlognn subvolume, where nn
corresponds to the currently running SYSnn.
Notes:
Operators can alter the volume used for log files.●
If you suspect that an operator has been switching between log file
subvolumes, use the OSM or TSM Event Viewer Application to look for
EMS file-switch events. You can use these events to trace your way
back through all subvolumes.
●
These files are used by customers, field service engineers, and the Global
Customer Support Center (GCSC) to diagnose problems.
To view messages in operator log ($0), use the EMS event viewer of your
choice:
EMSA●
EMSDIST●
OSM or TSM Event Viewer. See Viewing the Windows Event Viewer
Application Log Using OSM or TSM
●
ViewPoint●
Use the EMSCINFO collector information utility to display the current location