Reading and Interpreting S-Series System Log Files

ManualsBrandsHP ManualsServerHP Integrity NonStop Service Procedures

Reading and Interpreting S-Series System Log Files
This document describes the S-series server log files and how to read and interpret them. See
Change History for a list of changes made to this document.
The subsystems log messages to the following files (for more information about a file, click the file
name):
EMS Event Log Files Description
$SYSTEM.ZLOGnn.ZZEVnnnn The operator log file ($0) used for some
server subsystem and application EMS
event messages. Used by OSM and
TSM.
$SYSTEM.ZLOGnn.ZZEVCONF The configuration file for the operator log
($0) ZLOGnn subvols. Used by OSM and
TSM.
$SYSTEM.ZSERVICE.ZZSVnnnn Service ($ZLOG) EMS event logs. Used
by OSM and TSM.
$SYSTEM.ZSERVICE.ZZSKnnnn Alternate key files for the ZZSVnnnn files. 
Used by OSM and TSM.
$SYSTEM.ZSERVICE.ZZSVCONF The service EMS event log configuration
file. Used by OSM and TSM.
Other System Log Files
$SYSTEM.ZSERVICE.CPUHIST3 A processor status log. Used by TSM.
$SYSTEM.ZSERVICE.TSMERROR The TSM system resource model (SRM)
error event log.
$SYSTEM.ZSERVICE.ZZUSERS and
ZZUSERS2
The current and previous TSM user log
files.
OSM\bin\startsys.log and
TSM\bin\startsys.log
The low-level system startup messages
log.
Windows Event Viewer Application Log Application log for the Windows operating
system. Used by OSM and TSM.
Other Related Files
$SYSTEM.ZSERVICE.IAREPO A database file containing alarm history for
alarms created by OSM.
$SYSTEM.ZSERVICE.OSMCONF A text file containing configurable
parameters for all OSM server processes.
$SYSTEM.ZSERVICE.PERSIST A database of all current detailed TSM
alarm objects, containing the level of detail
seen in ZZAL* files, as well as pending
incident report (IR) objects.
$SYSTEM.ZSERVICE.PERSSUPP A database containing current TSM
configuration information.
$SYSTEM.ZSERVICE.SUPPREPO A database file containing dialout
configuration information. Used by OSM.

Summary of content (19 pages)

PAGE 1
Reading and Interpreting S-Series System Log Files This document describes the S-series server log files and how to read and interpret them. See Change History for a list of changes made to this document. The subsystems log messages to the following files (for more information about a file, click the file name): EMS Event Log Files $SYSTEM.ZLOGnn.ZZEVnnnn $SYSTEM.ZLOGnn.ZZEVCONF $SYSTEM.ZSERVICE.ZZSVnnnn $SYSTEM.ZSERVICE.ZZSKnnnn $SYSTEM.ZSERVICE.ZZSVCONF Other System Log Files $SYSTEM.ZSERVICE.
PAGE 2
$SYSTEM.ZSERVICE.ZCT08153 $SYSTEM.ZSERVICE.ZCT08458 $SYSTEM.ZSERVICE.ZZAAnnnn $SYSTEM.ZSERVICE.ZZALnnnn $SYSTEM.ZSERVICE.ZZDCnnnn $SYSTEM.ZSERVICE.ZZPSnnnn $SYSTEM.ZSERVICE.ZZSNnnnn $SYSTEM.ZSERVICE.ZZSSnnnn $SYSTEM.ZSERVICE.ZTRC* $SYSTEM.ZSERVICE.ZTRC A catalog containing a table used by the TSM client software for converting alarm and IR binary values into text strings. A catalog used by the resource access layer (RAL) of TSM when reporting errors.
PAGE 3
and status of the operator log ($0) files. In the output, look for the Current Log File field to determine where events are currently being logged. >EMSINFO $0, [DETAIL] Note: The DETAIL parameter option can be used to display additional information. For more information about an event viewer, see the appropriate manual or online help. For more information about operator messages, refer to the Operator Messages Manual. Top $SYSTEM.ZLOGnn.
PAGE 4
Messages Manual. Top $SYSTEM.ZSERVICE.ZZSVCONF ZZEVCONF files are configuration files that contain service log ($ZLOG) file tracking information. These files are defined by EMS collectors. System operators and service providers use this information to monitor the service log ($ZLOG) file status. For more information about the Event Management System (EMS), refer to the EMS Manual. Top $SYSTEM.ZSERVICE.ZZSKnnnn ZZSKnnnn files are alternate key files for the SSZV* files. Top Other System Log Files $SYSTEM.
PAGE 5
$SYSTEM.ZSERVICE.ZZUSERS and ZZUSERS2 The two TSM service application connection audit files in the $SYSTEM.ZSERVICE subvolume are ZZUSERS and ZZUSERS2. ZZUSERS is always the active audit file. When the maximum number of records for the ZZUSERS file is reached, the ZZUSERS file is copied over to the ZZUSERS2 file, a new ZZUSERS file is opened, and logging activity is resumed. These files are used by customers, service providers, the GCSC, or Development to determine: ● In RVUs prior to G06.
PAGE 6
You can use the FUP COPY command to view the ZZUSERS2 file. If the system is running G06.02 RVU or later, or if SPR T7945AAE is installed, you do not have to stop the $ZTSM process. You can copy the ZZUSERS file by using the SHARE option of the FUP COPY command: >FUP/OUT TEMP/COPY $SYSTEM.ZSERVICE.ZZUSERS,,SHARE >FUP COPY TEMP Top OSM\bin\startsys.log and TSM\bin\startsys.
PAGE 7
● On the taskbar, select Start> Settings> Control Panel, and double-click Administrative Tools and Event Viewer. In the control tree pane, click the log you want to view. For Windows NT: ● On the taskbar, select Start> Programs> Administrative Tools (Common)> Event Viewer. In the control tree pane, click the log you want to view. You can also view the Windows Event Viewer Application Log using the TSM service application or the OSM or TSM Low-Level Link Application.
PAGE 8
1. Use the file utility program (FUP) to rename PERSIST to PERSOLD. 2. Stop $ZTSM. Note that $ZTSM restarts automatically and creates a new PERSIST file. 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.
PAGE 9
To view alarm messages: 1. Log on to the server using the OSM Service Connection. 2. On the toolbar select Summary>Alarm. The Alarm Summary dialog box appears and displays a list of the current alarms. 3. For detailed information about an alarm message, select the message, and then click Detail. The Alarm Detail dialog box appears and displays: ● Name of the resource associated with the alarm. ● Whether the alarm dials out or not. ● Time and date the alarm occurred. ● Alarm type.
PAGE 10
current alarms. 3. For detailed information about an alarm message, select the message, and then click Show detail or Detail (depending on the TSM client version). The Alarm Detail dialog box appears and displays: ❍ Name of the resource associated with the alarm. ❍ Time and date the alarm occurred. ❍ Event type. ❍ Description of the alarm, including perceived severity, probable cause, and specific problem of the alarm.
PAGE 11
To load a snapshot: 1. Open the TSM Service Application or TSM Low-Level Link Application, but do not log on to the server. 2. Select File> Load snapshot. If you are logged on to a server, a dialog box will appear asking if you want to terminate that connection. To continue, click Yes. The Load Snapshot dialog box appears. 3. From the Snapshot File list, select the system name. If the system you want to load does not appear in the Snapshot File list, a snapshot has never been created for that server. 4.
PAGE 12
● ● ● A problem IR is created and another ZZSNnnnn file has not been created in the last 24 hours. When a periodic IR is created (every 14 days). When periodic IR is generated because of a user request from the Notification Director. The GCSC can use this file to help identify the source of the problem that caused the IR to be generated. To load a snapshot: 1. FTP the ZZSNnnnn file from the server to your workstation. 2. Start a new browser session. 3.
PAGE 13
register, revisions of boards, and scan string information (similar to the CPUMON7 process on K-series servers). These files are sent to the GCSC along with problem incident reports (IRs). GCSC and Development use the in-house Beguile tool to view the contents of these files for further analysis. Top $SYSTEM.ZSERVICE.ZTRC* ZTRC* files are text files containing user trace logs. These files are created and maintained by the main server process for OSM: the common information model object manager (CIMOM).
PAGE 14
$SYSTEM.ZOSM.LOGSCF LOGTSCF is a trace log created when the the ALTERIP command file is executed. Top $SYSTEM.ZOSM.LOGTCP0/1 LOGTCP0 is a trace log created when the the CTCPIP0 or INIT0 command file is executed. LOGTCP1 is a trace logs created when the CTCPIP1 or INIT1 command file is executed. Top $SYSTEM.ZOSM.LOGTCPIP LOGTCPIP is a trace log created when the ADDTCPIP command file is executed. Top $SYSTEM.SYSnn.
PAGE 15
Viewing the Windows Event Viewer Application Log Using OSM or TSM Using the TSM Service Application or the OSM or TSM Low-Level Link: ● Select Summary>Status Log, or ● After system discovery is complete, on the toolbar, ❍ In OSM, click ❍ In TSM, depending on the TSM client version, click Status Log or For detailed information about an event message, double-click on an event. The Event Detail dialog box appears and displays detailed information.
PAGE 16
Selecting Another Computer 1 Select Start>Run, type mmc, and click OK. 2 Select Console>Add/Remove Snap-in. The Add/Remove Snap-in window appears. 3 On the Standalone tab, click Add. The Add Standalone Snap-in window appears. 4 Select Event Viewer and click Add. The Select Computer dialog box appears. 5 Click Another Computer, and then enter the path and name of the computer, for example, \\domain name\computer name. 6 Click Finish, click Close, and then click OK.
PAGE 17
Gathering, Packaging, and Sending Files to the GCSC For Analysis When reporting problems, package and send the appropriate information to the Global Customer Support Center (GCSC) for analysis. The information you collect will be based on the problem being reported. Following are examples of the types of information you will need to collect. 1. Create a readme file that describes what you were doing at the time the error occurred and just prior to that time.
PAGE 18
Month mnemonics are: JA FE MR AP MY JU JY AG SE OC NO DE Example: Case 10-970321-1243 would have the directory name: MR211243 (If self-extracting, use extension .100. If non-self-extracting, use extension .1729.
PAGE 19
Change History for Reading and Interpreting S-Series System Log Files September 24, 2003 Added information about OSM server files. May 21, 2003 Updated instructions for using FUP copy to create an edit file and view the ZZUSERS file on systems prior to G06.02 without SPR T7945AAE. February 7, 2003 Updated topic for Windows NT and Windows 2000 Professional.