Runtime Diagnostics is a “point-in-time” diagnostics tool that detects problems that could be contributing to system issues RIGHT NOW with the goal of finding the problems in sixty seconds or less. It has been available since V1R12 and as of V1R13, diagnoses seven types of problems which are documented in this IBM Redbooks Publication http://www.redbooks.ibm.com/abstracts/sg248070.html?Open.
Is that all? Of course not! We are pleased to announce our eighth diagnostic event: JES2 Health Exceptions. This event is available starting in z/OS V2R1 with APAR OA46531. This will be added to the IBM Redbooks Publication at a later date but we wanted to make you aware of this option as soon as possible.
Runtime Diagnostics gathers information about the JES2 subsystem from the JES2 subsystem interface (SSI). Runtime Diagnostics analyzes the information received, determines a possible corrective action, and presents it to the caller on the system console, the hardcopy log, and optionally, to a sequential dataset. An example of a possible event appears below:
HZR0200I RUNTIME DIAGNOSTICS RESULT
REQ: 004 TARGET SYSTEM: SY1 HOME: SY1 2015/01/12
INTERVAL: 60 MINUTES
FOUND: 01 - PRIORITIES: HIGH:01 MED:00 LOW:00
EVENT 01: HIGH - JES2 - SYSTEM: SY1 2015/01/12
$HASP9158 JES2 PROCESSING STOPPED, $S NEEDED
ERROR: JES2 CANNOT PROCESS NEW WORK.
ACTION: $S TO ENABLE JES2 TO START PROCESSING NEW WORK.
The analysis for this new event is automatically incorporated into the existing processing. After Runtime Diagnostics has been started, issue the command F HZR,ANALYZE to now have all eight types of analysis performed. Additional information on this new event will also be available in z/OS V2R2 Problem Management when it is available.
Runtime Diagnostics is easy to use and there when you need it, but since it isn't needed very often, it's also easy to forget, so always remember the value of these tools - and that you have them almost literally at the end of your fingertips!