z/OS diagnostic data collection and analysis
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/...
| Autor principal: | |
|---|---|
| Autor Corporativo: | |
| Otros Autores: | |
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
San Jose, CA :
IBM, International Support Organization
c2005.
|
| Edición: | 1st edition |
| Colección: | IBM redbooks.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627346506719 |
Tabla de Contenidos:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. z/OS problem diagnosis fundamentals
- 1.1 Problem resolution steps
- 1.1.1 Identify the problem
- 1.1.2 Document the problem
- 1.1.3 Prioritize problem resolution
- 1.1.4 Analyze the problem
- 1.1.5 Ask for assistance
- 1.1.6 Implement the resolution
- 1.1.7 Close the problem
- 1.2 Problem severity
- Chapter 2. What version/release am I running?
- 2.1 Source of version and release information
- Chapter 3. Fundamental sources of diagnostic data
- 3.1 Diagnostic data sources
- 3.2 SYSLOG
- 3.3 OPERLOG
- 3.4 Logrec
- Chapter 4. Common problem types
- 4.1 Application program abends
- 4.2 System program abends
- 4.3 I/O errors
- 4.4 System wait states
- 4.5 System, subsystem, and application hangs
- 4.6 Hangs and loops
- 4.7 SYSTRACE, RMFMON, and SDSF
- 4.7.1 Displaying trace data for all ASIDs
- 4.7.2 RMF Monitor II
- 4.7.3 GRS contention
- 4.8 Program errors
- Chapter 5. MVS messages and codes
- 5.1 Message formats
- 5.2 Message examples
- 5.3 System codes
- 5.4 Wait state codes
- Chapter 6. SYS1.PARMLIB diagnostic parameters
- 6.1 IEAABD00, IEADMP00, and IEADMR00
- 6.1.1 SDATA options
- 6.1.2 PDATA options (only valid for IEADMP00)
- 6.2 SDATA and PDATA recommendation
- 6.3 IEADMCxx (dump command parameter library)
- 6.4 IEASLPxx (SLIP commands)
- Chapter 7. Cancelling tasks and taking dumps
- 7.1 Cancelling a task
- 7.2 Forcing a task
- 7.3 Dumping address spaces
- 7.3.1 DUMP command
- 7.4 Diagnostic data - dumps
- 7.4.1 ABEND dumps
- 7.5 SLIP dumps
- 7.5.1 SLIP using IGC0003E
- 7.5.2 SLIP using MSGID
- 7.6 SLIP dump using a z/OS UNIX reason code
- 7.6.1 Obtain a dump on a specific reason code
- 7.7 SNAP dumps.
- 7.7.1 Obtaining a SNAP dump
- 7.7.2 Customizing SNAP dumps
- 7.8 Stand-alone dumps
- 7.8.1 Allocating the stand-alone dump data set
- 7.8.2 SADMP program
- 7.8.3 ADMSADMP macro
- 7.8.4 Stand-alone dump procedure
- 7.8.5 SADMP processing
- 7.9 SVC dumps
- 7.10 Dump data set size
- 7.10.1 Allocating SYS1.DUMPxx data sets
- 7.10.2 Dynamic allocation of SVC dump data sets
- 7.11 Dumping multiple address spaces in a sysplex
- 7.11.1 Requesting a dump
- 7.12 Dump analysis and elimination (DAE)
- 7.13 Partial dumps
- 7.14 SDATA options
- Chapter 8. z/Architecture and addressing
- 8.1 Introduction to program status word (PSW)
- 8.1.1 Program status word details
- 8.2 What is addressability?
- 8.2.1 Format of the PSW
- 8.3 Is my dump from a z/OS 31-bit or 64-bit system?
- Chapter 9. z/OS trace facilities
- 9.1 Using the DISPLAY TRACE command
- 9.2 GTF trace
- 9.2.1 Defining the GTF trace options
- 9.2.2 Starting GTF
- 9.2.3 Stopping GTF
- 9.3 GTF tracing for reason code interrogation
- 9.4 Component trace
- 9.4.1 Parmlib members
- 9.4.2 Trace options
- 9.4.3 Collecting trace records
- 9.4.4 Starting component trace
- 9.4.5 Component trace for the logger address space
- 9.5 Master trace
- 9.5.1 Starting the master trace
- 9.6 GFS trace
- 9.7 System trace
- 9.8 SMS tracing
- Chapter 10. Interactive Problem Control System (IPCS)
- 10.1 Setting the IPCS defaults
- 10.1.1 Select the IPCS subcommand entry panel
- 10.1.2 What ASIDs have been dumped
- 10.2 VERBX MTRACE
- 10.3 SYSTRACE
- 10.3.1 Reviewing SYSTRACE data
- 10.4 IPCS SUMMARY command
- 10.5 What is VERBX?
- 10.5.1 IPCS VERBX LOGDATA command
- 10.6 IPCS virtual storage commands
- 10.7 Using IPCS to browse storage
- 10.8 Using IPCS to find the failing instruction
- 10.9 Searching IBM problem databases
- Chapter 11. CICS problem diagnosis.
- 11.1 Problem reference points
- 11.2 CICS messages
- 11.3 CICS abend codes
- 11.4 Analyzing CICS SVC dumps
- 11.5 CICS/TS 2.2 VERBEXIT options
- 11.6 CICS internal trace
- 11.7 CICS trace control facility
- Chapter 12. z/OS Language Environment
- 12.1 Run-time environment
- 12.1.1 Common LE messages
- 12.2 LE and batch (IMS, WebSphere, and so forth)
- 12.3 LE and CICS
- 12.3.1 Additional procedure for an SVCdump for 40xx abends under CICS
- 12.4 LE and UNIX System Services shell
- 12.5 Find failing module instructions
- 12.5.1 Reason code information
- 12.6 IPCS and Language Environment
- 12.7 Finding the failing CSECT name in LE
- Chapter 13. CICSPlex SM diagnostic procedures
- 13.1 Overview of the CICSPlex environment
- 13.2 Diagnostic aids
- 13.3 CICSPlex SM traces
- 13.4 CICSPlex SM component trace options
- 13.4.1 CMAS and MAS tracing
- 13.5 CICSPlex SM dumps
- 13.5.1 CICSPlex SM IPCS tools
- 13.6 CICSPlex SM module names, components and IPCS
- 13.6.1 Element type identifiers
- 13.6.2 CICSPlex SM component identifiers
- 13.6.3 The CICSPlex SM components and 3-character identifiers
- Chapter 14. DB2 problem diagnosis
- 14.1 System trace table
- 14.1.1 Master trace table
- 14.1.2 Common storage tracker
- 14.1.3 CHNGDUMP MAXSPACE
- 14.1.4 SDATA
- 14.1.5 What data to collect for DB2 problems
- 14.2 DB2 dump collection
- 14.3 Data sharing and IRLM
- 14.4 DB2 tracing
- 14.4.1 Trace output for DB2
- 14.5 DB2 dump diagnosis using IPCS
- Chapter 15. IMS diagnostic data collection
- 15.1 IMS diagnostic data
- 15.1.1 Batch message processing region
- 15.2 What must be kept to assist with IMS problem diagnosis
- 15.3 IMS and the MVS system trace table
- 15.3.1 IMS and the MVS master trace table
- 15.3.2 IMS dump space recommendations
- 15.4 IMS dump DD statements and FMTO
- 15.5 IMS tracing.
- 15.5.1 Tracing the BPE and CQS in an IMS environment
- 15.5.2 IMS APPC application program tracing
- 15.5.3 IMS TPIPE and OTMA traces
- 15.6 Simplify the dump process for multiple address spaces
- 15.7 Dumping IMS address spaces in a sysplex
- 15.8 IMS diagnostic data collection for WAIT/HANG conditions
- 15.8.1 IMS diagnostic data collection for a suspected Loop
- 15.8.2 IMS APPC diagnostic data capture procedures
- 15.9 IMS dump formatting using IPCS
- 15.9.1 IMS VERBX format option
- Chapter 16. VTAM diagnostic procedures
- 16.1 VTAM diagnostic commands
- 16.1.1 First failure support technology (FFST) for VTAM
- 16.2 VTAM IPCS dump formatting
- 16.2.1 VTAMMAP procedure
- 16.3 VTAM internal trace (VIT)
- 16.4 Recording traces in the internal table (MODE=INT)
- 16.5 Recording traces in the external table (MODE=EXT)
- 16.6 Module names in the internal trace records
- Chapter 17. TCP/IP component and packet trace
- 17.1 Tracing to the TCP/IP data space
- 17.2 PKTTRACE parms
- 17.3 Tracing to the external writer
- 17.3.1 Starting an external writer
- 17.3.2 CTRACE step (component SYSTCPIP)
- 17.3.3 Multiple trace (CTRACE and packet) step
- 17.3.4 Stopping the packet trace
- Chapter 18. CICS Transaction Gateway on z/OS
- 18.1 Gateway daemon
- 18.1.1 The Gateway daemon components
- 18.2 CTG trace file allocation
- 18.3 CICS Transaction Gateway application trace
- 18.4 Gateway daemon trace
- 18.5 JNI tracing
- 18.6 EXCI trace
- 18.6.1 Enable a GTF trace
- Chapter 19. WebSphere MQSeries z/OS diagnostic procedures
- 19.1 WebSphere MQSeries for z/OS
- 19.2 Dumping MQ MSTR, MQ CHIN and CHIN data space
- 19.3 MQ tracing using GTF
- 19.3.1 Starting GTF
- 19.4 WebSphere MQSeries z/OS channel trace
- 19.5 IPCS and WebSphere MQSeries z/OS
- 19.5.1 Using IPCS for WebSphere MQSeries
- 19.6 WebSphere MQ JAVA tracing.
- 19.7 Taking JMS traces within WebSphere
- Chapter 20. WebSphere Business Integration Message Broker on z/OS
- 20.1 Components of WBI message broker on z/OS
- 20.2 Address spaces that interact with the broker
- 20.3 Dumps captured by WBI message broker
- 20.4 Reviewing a WBI message broker dump
- 20.5 Dumping the WBI message broker address spaces
- 20.6 Displaying the status of a trace
- 20.7 WBI message broker user execution group trace
- 20.8 WBI message broker execution group trace
- 20.9 WBI message broker service trace
- 20.10 WBI message broker useful output files
- 20.11 Useful HFS files
- 20.12 WBI Message Broker for z/OS trace files
- Chapter 21. WebSphere Application Server for z/OS
- 21.1 WebSphere on z/OS diagnostic data
- 21.1.1 WebSphere Application Server joblog and syslog
- 21.1.2 Dumping the WebSphere Application Server address spaces
- 21.2 WebSphere Application Server CTRACE (SYSBBOSS)
- 21.2.1 Executing the CTRACE for WebSphere
- 21.3 LDAP trace
- 21.3.1 Starting an LDAP trace
- 21.3.2 IBM HTTP Server logs and trace
- 21.4 JVM debugging tools for z/OS
- Chapter 22. Distributed platform problem determination
- 22.1 What release am I running?
- 22.2 AIX tracing and core dumps
- 22.2.1 tcpdump and iptrace
- 22.2.2 UNIX systems core dump analysis
- 22.2.3 Generating a core dump
- 22.2.4 Looking at a system core dump
- 22.2.5 Ensuring that a good core file is generated
- 22.2.6 errpt command
- 22.3 WebSphere Application Server
- 22.3.1 Reviewing the JVM logs
- 22.3.2 Interpreting the JVM log data
- 22.3.3 Collector tool
- 22.4 Debugging with the Application Server toolkit
- 22.5 WebSphere Application Server tracing
- 22.5.1 Enabling tracing
- 22.5.2 Enabling trace at server startup
- 22.5.3 Enabling trace on a running server
- 22.5.4 Enabling trace on an application client or stand-alone process.
- 22.5.5 JMS tracing within WebSphere.
