You are previewing z/OS Diagnostic Data Collection and Analysis.
O'Reilly logo
z/OS Diagnostic Data Collection and Analysis

Book Description

This IBM Redbook describes problem diagnosis fundamentals and analysis methodologies for the z/OS system. It provides guidelines for the collection of relevant diagnostic data, tips for analyzing the data, and techniques to assist in identifying and resolving of Language Environment, CICS, CICSPlex/SM, MQSeries, VTAM, and DB2 problems. Also described are some diagnostic procedures that are not purely z/OS, but that are related to the various platforms (UNIX and Windows) where IBM software executes and interacts with z/OS in a Client/Server or distributed framework topology.
This document shows you how to:
- Adopt a systematic and thorough approach to dealing with problems
- Identify the different types of problems
- Determine where to look for diagnostic information and how to obtain it
- Interpret and analyze the diagnostic data collected
- Escalate problems to the IBM Support Center when necessary
Diagnostic data collection and analysis is a dynamic and complex process. This redbook shows you how to identify and document problems, collect and analyze pertinent diagnostic data and obtain help as needed, to speed you on your way to problem resolution.

Table of Contents

  1. Copyright
  2. Preface
  3. z/OS problem diagnosis fundamentals
    1. Problem resolution steps
    2. Problem severity
  4. What version/release am I running?
    1. Source of version and release information
  5. Fundamental sources of diagnostic data
    1. Diagnostic data sources
    2. SYSLOG
    3. OPERLOG
    4. Logrec
  6. Common problem types
    1. Application program abends
    2. System program abends
    3. I/O errors
    4. System wait states
    5. System, subsystem, and application hangs
    6. Hangs and loops
    7. SYSTRACE, RMFMON, and SDSF
    8. Program errors
  7. MVS messages and codes
    1. Message formats
    2. Message examples
    3. System codes
    4. Wait state codes
  8. SYS1.PARMLIB diagnostic parameters
    1. IEAABD00, IEADMP00, and IEADMR00
    2. SDATA and PDATA recommendation
    3. IEADMCxx (dump command parameter library)
    4. IEASLPxx (SLIP commands)
  9. Cancelling tasks and taking dumps
    1. Cancelling a task
    2. Forcing a task
    3. Dumping address spaces
    4. Diagnostic data - dumps
    5. SLIP dumps
    6. SLIP dump using a z/OS UNIX reason code
    7. SNAP dumps
    8. Stand-alone dumps
    9. SVC dumps
    10. Dump data set size
    11. Dumping multiple address spaces in a sysplex
    12. Dump analysis and elimination (DAE)
    13. Partial dumps
    14. SDATA options
  10. z/Architecture and addressing
    1. Introduction to program status word (PSW)
    2. What is addressability?
    3. Is my dump from a z/OS 31-bit or 64-bit system?
  11. z/OS trace facilities
    1. Using the DISPLAY TRACE command
    2. GTF trace
    3. GTF tracing for reason code interrogation
    4. Component trace
    5. Master trace
    6. GFS trace
    7. System trace
    8. SMS tracing
  12. Interactive Problem Control System (IPCS)
    1. Setting the IPCS defaults
    2. VERBX MTRACE
    3. SYSTRACE
    4. IPCS SUMMARY command
    5. What is VERBX?
    6. IPCS virtual storage commands
    7. Using IPCS to browse storage
    8. Using IPCS to find the failing instruction
    9. Searching IBM problem databases
  13. CICS problem diagnosis
    1. Problem reference points
    2. CICS messages
    3. CICS abend codes
    4. Analyzing CICS SVC dumps
    5. CICS/TS 2.2 VERBEXIT options
    6. CICS internal trace
    7. CICS trace control facility
  14. z/OS Language Environment
    1. Run-time environment
    2. LE and batch (IMS, WebSphere, and so forth)
    3. LE and CICS
    4. LE and UNIX System Services shell
    5. Find failing module instructions
    6. IPCS and Language Environment
    7. Finding the failing CSECT name in LE
  15. CICSPlex SM diagnostic procedures
    1. Overview of the CICSPlex environment
    2. Diagnostic aids
    3. CICSPlex SM traces
    4. CICSPlex SM component trace options
    5. CICSPlex SM dumps
    6. CICSPlex SM module names, components and IPCS
  16. DB2 problem diagnosis
    1. System trace table
    2. DB2 dump collection
    3. Data sharing and IRLM
    4. DB2 tracing
    5. DB2 dump diagnosis using IPCS
  17. IMS diagnostic data collection
    1. IMS diagnostic data
    2. What must be kept to assist with IMS problem diagnosis
    3. IMS and the MVS system trace table
    4. IMS dump DD statements and FMTO
    5. IMS tracing
    6. Simplify the dump process for multiple address spaces
    7. Dumping IMS address spaces in a sysplex
    8. IMS diagnostic data collection for WAIT/HANG conditions
    9. IMS dump formatting using IPCS
  18. VTAM diagnostic procedures
    1. VTAM diagnostic commands
    2. VTAM IPCS dump formatting
    3. VTAM internal trace (VIT)
    4. Recording traces in the internal table (MODE=INT)
    5. Recording traces in the external table (MODE=EXT)
    6. Module names in the internal trace records
  19. TCP/IP component and packet trace
    1. Tracing to the TCP/IP data space
    2. PKTTRACE parms
    3. Tracing to the external writer
  20. CICS Transaction Gateway on z/OS
    1. Gateway daemon
    2. CTG trace file allocation
    3. CICS Transaction Gateway application trace
    4. Gateway daemon trace
    5. JNI tracing
    6. EXCI trace
  21. WebSphere MQSeries z/OS diagnostic procedures
    1. WebSphere MQSeries for z/OS
    2. Dumping MQ MSTR, MQ CHIN and CHIN data space
    3. MQ tracing using GTF
    4. WebSphere MQSeries z/OS channel trace
    5. IPCS and WebSphere MQSeries z/OS
    6. WebSphere MQ JAVA tracing
    7. Taking JMS traces within WebSphere
  22. WebSphere Business Integration Message Broker on z/OS
    1. Components of WBI message broker on z/OS
    2. Address spaces that interact with the broker
    3. Dumps captured by WBI message broker
    4. Reviewing a WBI message broker dump
    5. Dumping the WBI message broker address spaces
    6. Displaying the status of a trace
    7. WBI message broker user execution group trace
    8. WBI message broker execution group trace
    9. WBI message broker service trace
    10. WBI message broker useful output files
    11. Useful HFS files
    12. WBI Message Broker for z/OS trace files
  23. WebSphere Application Server for z/OS
    1. WebSphere on z/OS diagnostic data
    2. WebSphere Application Server CTRACE (SYSBBOSS)
    3. LDAP trace
    4. JVM debugging tools for z/OS
  24. Distributed platform problem determination
    1. What release am I running?
    2. AIX tracing and core dumps
    3. WebSphere Application Server
    4. Debugging with the Application Server toolkit
    5. WebSphere Application Server tracing
    6. WebSphere MQ on UNIX and Windows
    7. WebSphere Business Integration Message Broker
    8. Lightweight Directory Access Protocol (LDAP)
    9. IBM DB2 UDB on UNIX and Windows
    10. WebSphere TXSeries (CICS for UNIX and Windows)
    11. The SYMREC file
    12. Encina trace messages
    13. DCE diagnostic data
    14. DCE/DFS core files
    15. DCE/DFS process hangs or loops
    16. TXSeries CICS dump format utility (cicsdfmt)
    17. TXSeries CICS trace format utility (cicstfmt)
    18. WebSphere TXSeries tracing
    19. TXSeries CICS auxiliary trace facility
    20. Encina tracing for CICS application server processes
    21. Writing trace data to in-storage buffers
    22. CICS universal client
    23. Starting and stopping client daemon tracing
    24. Wrapping the client daemon trace
    25. Formatting the binary trace file (CICSFTRC)
    26. Client daemon trace analysis
    27. CICS Transaction Gateway tracing
  25. Related publications
    1. IBM Redbooks
    2. Other publications
    3. Online resources
    4. How to get IBM Redbooks
    5. Help from IBM
  26. Back cover
  27. Index