Abstract for JES2 Diagnosis
z/OS Version 2 Release 1 summary of changes
Identifying the problem
Abends
Reasons for a JES2 abend
Description of message $HASP088
Initialization problems
For any error
JES2 stops or loops
JES2 issues $HASP479
An abend occurs
Initialization statement errors
JES2 does not start
Checkpoint reconfiguration diagnostic procedures
JES2 checkpoint reconfiguration diagnostic messages
Error messages
Tracking messages
Processing delayed messages
Information needed to debug a checkpoint reconfiguration error
Waits
Output problems
Print services facility (PSF) printer problems
Looping problems
Disastrous errors
Resource shortages
$HASP050 message for resource shortages
$HASP050 message for CMBs - console message buffers
Examine LOGREC Data
Analyze the Dump Using IPCS
$HASP050 message for JQEs - job queue elements
$HASP050 message for TGs - spool space and track groups
Remote (RJE) and node (NJE) problems
Problems common to RJE and NJE
Node or remote status is draining for several minutes
Erroneous I/O errors
Bind image failure
Unable to establish connection
NJE problems
Unable to establish connection
Output remains on your node
Recreating NJE problems
Data space errors
Performance problems
Problems applying maintenance
Collecting problem data
Basic information to collect
Additional information you might need
Establishing JES2 traces
Setting up a JES2 trace environment with CTRACE
Setting up a JES2 trace environment at initialization
Setting up a JES2 trace environment using commands
Summary of trace identifiers
Modifying the JES2 trace environment
Trace output samples
Trace ID=0 sample
Trace ID=1, ID=2, ID=18, and ID=19 sample
Trace record contents
Trace ID=3 sample
Trace record contents
Trace ID=4 sample
Trace record contents
Trace ID=5 sample
Trace ID=6 and ID=7 sample
Trace record contents
Trace ID=8, ID=9 and ID=10 sample
Trace record contents
Trace ID=11 and ID=12 sample
Trace ID=13 sample
Trace record contents
Trace ID=14 and ID=15 sample
Trace record contents
Trace ID=16 sample
Trace record contents
Trace ID=17 sample
Trace record contents
Trace ID=20 sample
Trace record contents
Trace ID=21 sample
Trace record contents
Trace ID=22 sample
Trace record contents
Trace ID=23 sample
Trace record contents
Trace ID=24 sample
Trace record contents
Trace ID=25 sample
Trace ID=26 sample
Trace record contents
Trace ID=27 sample
Trace ID=28 sample
Trace ID=29 sample
Trace ID=30 sample
Trace record contents
Trace ID=31 sample
Trace record contents
Trace ID=32 sample
Trace ID=33 sample
Trace ID=34 sample
Trace ID=35 sample
Trace ID=36 sample
Trace ID=37 sample
Trace ID=38 sample
Trace ID=39 sample
Trace ID=40 sample
Trace ID=41 sample
Trace ID=42 sample
Trace ID=43 sample
Trace ID=44 sample
Trace ID=45 sample
Trace ID=46 sample
Installation-defined trace events
Creating a trace table using the $TRACE macro
Storage considerations
Using the JES2 DEBUG facility
Starting and stopping the DEBUG facility
Determine why JES2 issued a $HASP186 message
Using IPCS for diagnosis
Provide for JES2 IPCS Support
Dump level - diagnosing level considerations
JES2 IPCS support install verification
Procedure to verify your JES2 IPCS support level
Ensure you have the correct JES2 IPCS PARMLIB member
Ensure you have the correct JES2 IPCS panel library
Ensure you have the correct JES2 SHASMIG library
Using IPCS panels to analyze JES2 data in a dump
Using the CBFORMAT command to display JES2 control blocks
Using IPCS in batch or line mode
Assuring JES2 can be serviced using IPCS
Using symptom records for diagnosis
Controlling operator notification of JES2 symptom records
Where to find JES2 symptom records
Using IPCS to analyze JES2 symptom records
Reporting information from the symptom record to IBM
JES2 symptom records
Diagnostic procedures for $WTO PARAMETER LIST ERROR symptom records
Finding the data
Determining why JES2 created a symptom record
Correcting the error
JES2 Health Monitor
Monitor processing
Setting up the monitor
Monitor Alert Messages
Monitor notices
Resource monitoring
Monitor commands
Reporting the problem