Reading and Interpreting S-Series System Log Files

Use the file utility program (FUP) to rename PERSIST to PERSOLD.1.
Stop $ZTSM. Note that $ZTSM restarts automatically and creates a
new PERSIST file.
2.
Note: Undelivered IRs in PERSOLD will not be delivered.
Top
$SYSTEM.ZSERVICE.PERSSUPP
PERSSUPP is a database that contains the current TSM software
configuration information.
For G06.04 and later RVUs, PERSSUPP is created by the TSM Notification
Director Application. For G06.03 and earlier RVUs, PERSSUPP is created by
the TSM Configuration Application.
Development can use the information to assist with problem analysis related
to the TSM software.
Top
$SYSTEM.ZSERVICE.SUPPREPO
SUPPREPO is a database file containing dialout configuration information. This
file is created and maintained by the OSM incident analysis provider (IAPRVD).
Top
$SYSTEM.ZSERVICE.ZCT08153
This file is a catalog containing a table used by the TSM client for converting
alarm and incident report (IR) binary values into text strings.
Top
$SYSTEM.ZSERVICE.ZCT08458
This file is a catalog used by the TSM resource access layer (RAL) when
reporting errors. It contains a table for converting binary values into text
strings.
The RAL provides service clients with access to system resources in a
system-independent manner.
Top
$SYSTEM.ZSERVICE.ZZAAnnnn
ZZAAnnnn files are attachment files created for each OSM alarm. These files
are created by the OSM incident analysis provider (IAPRVD).
The ZSERVICE.ZZAAnnnn files are generated when OSM incident analysis
(IA) detects and generates alarms. Each ZZAAnnnn file contains one alarm.
ZZAAnnnn files are text files with code 101, where nnnn is 0000 through
9999. The following information is logged: Resource Name, Description, Alert
Type, Perceived Severity, Probable Cause, Creation Time and Repair
Actions.