Contents

Preface
Who this book is for
Notes on terminology
CICS system connectivity
Summary of changes
Changes made to this book for CICS Transaction Server for z/OS, Version 3 Release 1
Changes made to this book for CICS Transaction Server for z/OS, Version 2 Release 3
Changes to this book for CICS Transaction Server for OS/390 Release 3
Figures
Tables
Approach to problem determination
Introduction
What is problem determination?
How this book can help you
CICSPlex SM system overview
The structure of CICSPlex SM
The Web User Interface
The ISPF end-user interface
CMAS networks and registration
The structure of the CMAS
The agents in a MAS
The ESSS and data spaces
Common components
Kernel Linkage
Trace Services
Message Services
Common Services
Data Cache Manager
Queue Manager
Data Repository
Communications
Identifying a problem
Has CICSPlex SM run successfully before?
Have any changes been made since the last successful run?
Are there any messages that could explain the problem?
Does the problem occur at specific times?
Does the problem affect specific parts of the environment?
Common types of problem
Sources of information
Your own documentation
Change log
Manuals
Online diagnostic aids
Messages
Symptom strings
LOGREC records
Traces
Tools for problem determination
Using trace
The CMAS and MAS trace facilities
Tracing in a CMAS
Tracing in a MAS
Types and levels of tracing
Controlling the amount of tracing in a CMAS or MAS
Using the end-user interface to control tracing
Interpreting CMAS and MAS trace entries
Formatting CMAS and MAS trace entries
Trace formatting options on the host
Trace formatting JCL
The CAS LU 6.2 communications trace
Tracing LU 6.2 communications
Interpreting the LU 6.2 communications trace
Web User Interface trace services
Setting trace flags using the WUITRACE parameter
Setting trace flags through COVC
The available trace flags
Exception traces
Using dumps
Unexpected dumps
CICSPlex SM dumps under MVS
CICSPlex SM dumps under CICS
CICSPlex SM-requested dumps
Abends in the CAS
CMAS initialization failures
MAS initialization failures
ESSS program call (PC) routine failures
User-requested dumps
Using the MVS DUMP command
Using the ISPF end-user interface
Managing dumps in MVS
Using dumps with the Web User Interface
The available dump codes
Displaying and formatting dumps with IPCS
Using the CICSPlex SM dump formatting routine
Formatting a CICSPlex SM SDUMP
Using the ESSS utility (EYU9XEUT)
The EYU9XEUT options
Dumping data structures (DUMP)
Reloading broadcast functions (RELOAD)
Stopping the ESSS (TERMINATE)
The EYU9XEUT JCL
Using the ESSS Information Display Utility (EYU9XENF)
Using the online utility transaction (COLU)
The COLU transaction
Valid keywords for component CHE
Valid keywords for component COM
Valid keywords for component KNL
Valid keywords for component QUE
Valid keywords for component SRV
Valid keywords for component TOP
Using the interactive debugging transactions (COD0 and CODB)
Running the debugging transactions
Method-level debugging with COD0
Issuing commands recursively
Issuing commands that alter CICSPlex SM
ALLOC (allocating a resource)
ATTACH (attaching a method)
CALL (calling external CICS programs and transactions)
CAPTURE (capturing and printing a view)
DUMP (displaying and altering data)
EXEC (executing a method)
EXIT (exiting COD0)
HELP (getting online help)
LIST (listing tasks and allocated resources)
POST (posting an ECB)
PRINT (printing data areas under CICS/ESA, CICS TS)
PURGE (purging an allocated resource)
START (starting a method in the CMAS)
TRACE (setting CICS and CICSPlex SM trace flags)
TRACK (setting trace flags by calling structure)
TRAP (setting trace flags for a method)
Displaying a MAL from COD0
System-level debugging with CODB
CODB commands
The COMP ID field
The ADDR field
The ALET field
The PF Key prompts
The MSG field
The memory display area
CODB altering memory
Accessing CODB from COD0
Using PlexManager diagnostic facilities
The DIAGxxxx views
DIAGMSG (Diagnostic facilities)
DIAGSESS (Connected sessions)
DIAGSYS (Connected CASs)
Extended diagnostic mode
Status messages
Internal tracing
Disabling error recovery
Investigating and documenting a problem
Abends, stalls, and bottlenecks
Investigating abends
MVS abends
CICS abends
Investigating stalls
An undetermined stall condition
A suspected loop
A suspected wait
Investigating bottlenecks
Investigating output and system management problems
Incomplete operations data returned
No entry in the MAS view
INACTIVE status
ACTIVE status
Missing monitor data
Unexpected real-time analysis results
An example SAM problem
An example MRM problem
Unexpected workload management routing decision
Is dynamic routing enabled?
Which workload is active?
Is the workload being separated?
Application programming interface problems
Investigating Web User Interface problems
Server and browser messages
Server messages
Browser messages
COVC status panel
COVC debugging commands
Running the COVC transaction for debugging
Typical end-user problems
Working with IBM to solve a problem
IBM Program Support
When to contact the Support Center
Working with the Support Center
What the Support Center needs to know
What happens next
APARs, fixes, and PTFs
The APAR process
Collecting the documentation for an APAR
Documentation needed for problems with CICSPlex SM
Sending the documentation to IBM
Applying the fix
The APAR becomes a PTF
Appendixes
Appendix A. CICSPlex SM naming standards
The format of names
Element type identifiers
Component identifiers
Major components of CICSPlex SM
Appendix B. System parameters for problem determination
Specifying system parameters
The problem determination parameters
Bibliography
The CICS Transaction Server for z/OS library
The entitlement set
PDF-only books
Other CICS books
Accessibility
Index
Notices
Programming interface information
Trademarks
[[ Contents Previous Page | Next Page Index ]]