HP XP Command View Advanced Edition Software - Manual (Page 203)

9 Collecting trace information and logs
This chapter describes collecting trace information and logs for Smart Manager for Mainframe.
Information that can be used for troubleshooting
If an error occurs, trace information and logs can be used for troubleshooting.
The following table shows the information that can be used for troubleshooting.
Table 50 Information that can be used for troubleshooting
Description
Information that can be
used for troubleshooting
Trace information includes user operations and macros issued to the storage system. It is saved in
memory and can be used to help analyze the causes of errors. In Smart Manager for Mainframe, trace
information saved in memory is output to an ABEND dump if a CLI command terminates abnormally.
Trace information
• Error messages and trace information (event log) are collected in log datasets.
• Log data for the CLI commands executed in the ISPF panel are collected in ISPF log dataset.
• CLI command-execution logs are collected in SYSLOG.
Logs
Related topics
• Collecting trace information , page 203
• Log types for Smart Manager for Mainframe , page 204
Collecting trace information
Trace information about user operations and macros issued to hardware is saved in memory. To help
analyze the causes of errors, the trace information can be specified to be output to an ABEND dump
if a CLI command terminates abnormally.
If GTF is started with the GTF parameter specified to acquire an USR trace (TRACE=USR), trace
information will be acquired as a GTF trace with an event code from X'300' to X'30F'.
Collecting trace information when using scripts
To output ABEND dumps when using scripts to operate Smart Manager for Mainframe, specify
SYSABEND for a JCL DD statement.
Collecting trace information when using TSO/E
The following describes how to output ABEND dumps when using TSO/E to operate Smart Manager
for Mainframe.
User Guide 203