Explanation
Where
text is:
RUNTIME DIAGNOSTICS RESULTSUMMARY: text
REQ: RequestId
SYSTEM: SystemName
HOME: SystemHome hh:mm:ss - yyyy/mm/dd
INTERVAL: text
EVENTS: text
FOUND: nn
- PRIORITIES: HIGH=nn
MED=nn
LOW=nn
TYPES: I/O=nn
USS=nn
XCF=nn
CF=nn
XES=nn
OPERLOG=nn
LATCH=nn
ASID=nn
RESULTS: text
ErrorDataRC=nn
RS=nn
This message displays the
Runtime Diagnostic results. For more information, see the topic on Runtime Diagnostics symptoms in z/OS Problem Management.
If additional component-specific messages follow, see the explanation
for that message.
In the message fields:
- SUMMARY: text
- The text field contains one of the following:
- SUCCESS - Runtime Diagnostics completed successfully.
- QUALIFIED SUCCESS - SOME PROCESSING FAILED - Runtime Diagnostics
completed with some failures.
- FAILED - ALL PROCESSING FAILED - Runtime Diagnostics did not complete.
It failed.
- SUCCESS - NO EVENTS FOUND - Runtime Diagnostics completed successfully.
- QUALIFIED SUCCESS - SOME PROCESSING BYPASSED - Runtime Diagnostics
completed successfully.
- REQ: RequestId
- The unique number that identifies this instance of Runtime Diagnostics.
- SYSTEM: SystemName
- The name of the system diagnosed by Runtime Diagnostics.
- HOME: systemhome
- The name of the home system on which Runtime Diagnostics is running.
- hh:mm:ss - yyyy/mm/dd
- The date and local time of Runtime Diagnostics output. The date
is represented as year/month/day, and the time is represented as hours
(00–23), minutes (00–59), and seconds (00–59).
- INTERVAL: Interval
- The number of minutes back from request time that diagnosis starts.
- EVENTS:
- A list of the events that were found and diagnosed by Runtime
Diagnostics.
- FOUND: nn
- The number of events that were found and diagnosed by Runtime
Diagnostics.
- PRIORITIES: HIGH=nn MED=nn LOW=nn
- HIGH= The number of high priority events that were diagnosed
by Runtime Diagnostics.
- MED= The number of medium priority events that were diagnosed
by Runtime Diagnostics.
- LOW= The number of low priority events that were diagnosed
by Runtime Diagnostics.
- TYPES:
- The type and number of events found and diagnosed by Runtime Diagnostics.
- I/O=nn
- I/O error events diagnosed.
- USS=nn
- z/OS® UNIX System Services error events diagnosed.
- XCF=nn
- Cross-system coupling facility (XCF) error events diagnosed.
- CF=nn
- Coupling facility (CF) error events diagnosed.
- XES=nn
- Cross-system extended services (XES) error events diagnosed.
- OPERLOG=nn
- Operations log (OPERLOG) error events diagnosed.
- LATCH=nn
- Latch error events diagnosed.
- ASID=nn
- Address space error events diagnosed.
- LOCK=nn
- Address space has high local lock suspension rate.
- RESULTS: text
- The text field contains one the following results of Runtime Diagnostics
processing:
- PROCESSING BYPASSED: type
- Runtime Diagnostics processing bypassed one or more of the following
events:
- PROCESSING FAILURES: type
- Runtime Diagnostics failed processing one or more of the following
type of events:
- I/O
- Failure occurred processing I/O events.
- USS
- Failure occurred processing z/OS UNIX System Service events.
- XCF
- Failure occurred processing XCF events.
- CF
- Failure occurred processing CF events.
- XES
- Failure occurred processing XES events.
- OPERLOG
- Failure occurred processing OPERLOG events.
- LATCHES
- Failure occurred processing LATCH events.
- ASID
- Failure occurred processing ASID events.
- PAGERATE
- Failure occurred processing PAGING events.
- HIGHCPU
- Failure occurred processing HIGHCPU events.
- STORAGE
- Failure occurred processing STORAGE events.
- DUMP
- Failure occurred processing DUMP events.
- SYSTEM
- Failure occurred processing SYSTEM events.
- CONS
- Failure occurred processing CONSOLE events.
- LOOP
- Failure occurred processing LOOP events.
- ENQ
- Failure occurred processing ENQ events.
- LOCK
- Failure occurred processing LOCK events.
- ErrorData
- Text which describes an error being reported by internal processing.
- RC=nn
- The return code.
- RS=nn
- The reason code
System action
The system continues processing.
Operator response
If a condition exists, follow the recommended
action.
System programmer response
If a condition exists, follow the
recommended action.
Source
Module
Routing code
Descriptor code