Runtime Diagnostics DEBUG options

Purpose

Restriction: Do not enable the debug option unless under the direction of IBM® support.

If IBM Service determines they need more Runtime Diagnostics data, they might request that you specify the debug options. The MODIFY HZR,ANALYZE,SYSNAME=XXXXXXX,DEBUG=(XXXXXXX,XXXXXXX) command initiates an SVC dump to collect addition problem data.
Note: If the DEBUG option is requesting when there is no event detected, only the Runtime Diagnostics address space is dumped. If the DEBUG option is requested when an event is detected, both the HZR address space and the specific address spaces that are identified in the events are dumped.

Tip: Before using this option, ensure that the system is able to take an SVC dump. To determine which dump options are currently in effect, use the DISPLAY DUMP command.

Format

MODIFY HZR,ANALYZE,[SYSNAME=SYSNAME]([,DEBUG=ALL)|(LOOP|NOLOOP),(ENQ|NOENQ),
(LOCK|NOLOCK),(HIGHCPU|NOHIGHCPU),(MSGS|NOMSGS),(OMVS|NOOMVS),(LATCH|NOLATCH)])

Options

SYSNAME
The target system that Runtime Diagnostics analyzes. By default, all analysis is conducted against the home system.
Note: When the target system is not the home system, Runtime Diagnostics processes only the following debug options:
  • ALL
  • ENQ
  • NOENQ
  • MSGS
  • NOMSGS
DEBUG
Indicates conditions under which Runtime Diagnostics initiates an SVC dump of the HZR address space and the address spaces that are associated with events displayed in message HZR0200I. Up to 15 address spaces can be reported in the dump. The debug option controls only when the system dump occurs; the debug option does not provide analysis of Runtime Diagnostics processing.
When entering two or more debug options, use parenthesis except with ALL, which is mutually exclusive. For example:
  • F HZR,ANALYZE,DEBUG=ALL
  • F HZR,ANALYZE,DEBUG=(LOOP,NOENQ)
Remember: Use the debug option only when under the direction of IBM Service.
ALL
Start of changeRuntime Diagnostics initiates an SVC dump of the HZR address spaces of 15 address spaces and the 15 address spaces associated with each LOOP, HIGHCPU, ENQ, LOCK, OMVS and LATCH event that is displayed in message HZR0200I.
Note: The keyword ALL supersedes all other keywords. For Example, if you specify both All and MSG on the ANALYZE command, F HZR,ANALYZE,DEBUG=(ALL,MSGS), MSGS is ignored.
End of change
LOOP
Start of changeRuntime Diagnostics initiates an SVC dump of the HZR address space, along with a maximum of 15 address spaces that are associated with each LOOP event that displays in the HZR0200I message. If any data spaces exist for the address spaces dumped, they are also included in the dump.End of change
NOLOOP
Start of changeWhen no LOOP events are found during the ANALYZE request, Runtime Diagnostics dumps the HZR address space.End of change
ENQ
Start of changeRuntime Diagnostics initiates an SVC dump of the HZR address space along with a maximum of 15 address spaces that are associated with each ENQ event that displays in the HZR0200I message. If any data spaces exist for the address spaces dumped, they are also included in the dump.End of change
NOENQ
Start of changeWhen no ENQ events are found during the ANALYZE request, Runtime Diagnostics dumps the HZR address space.End of change
LOCK
Start of changeRuntime Diagnostics initiates an SVC dump of the HZR address space along with a maximum of 15 address spaces that are associated with each LOCK event that displays in the HZR0200I message. If any data spaces exist for the address spaces dumped, they are also included in the dump.End of change
NOLOCK
Start of changeWhen no LOCK events are found during the ANALYZE request,End of change
HIGHCPU
Start of changeRuntime Diagnostics initiates an SVC dump of the HZR address space along with a maximum of 15 address spaces that are associated with each HIGHCPU event that displays in the HZR0200I message. If any data spaces exist for the address spaces dumped, they are also included in the dump.End of change
NOHIGHCPU
Start of changeWhen no HIGHCPU events are found during the ANALYZE request, Runtime Diagnostics dumps the HZR address space.End of change
MSGS
Start of changeRuntime Diagnostics dumps the HZR address space when MESSAGE events are found during the ANALYZE request.End of change
NOMSGS
Start of changeRuntime Diagnostics dumps the HZR address space when no MESSAGE events are found during the ANALYZE request.End of change
OMVS
Start of changeRuntime Diagnostics initiates an SVC dump of the HZR address space, along with a maximum of 15 address spaces that are associated with each OMVS event that displays in the HZR0200I message. If any data spaces exist for the address spaces dumped, they are also included in the dump.End of change
NOOMVS
Start of changeWhen no OMVS events are found during the ANALYZE request, HZR dumps the HZR address space.End of change
LATCH
Start of changeRuntime Diagnostics initiates an SVC dump of the HZR address space along with a maximum of 15 address spaces that are associated with each LATCH event that displays in the HZR0200I message. If any data spaces exist for the address spaces dumped, they are also included in the dump.End of change
NOLATCH
Start of changeWhen NO LATCH events are found, Runtime Diagnostics dumps the HZR address space .End of change

Examples

Example:
Runtime Diagnostics shows a job consuming a high amount of CPU, but your monitors are not showing the job that is consuming high CPU. If instructed by IBM Service, add the following debug option to the MODIFY command the next time Runtime Diagnostics runs: 
F HZR,ANALYZE,DEBUG=HIGHCPU
If Runtime Diagnostics highlights the job with a HIGHCPU event, it initiates an SVC dump of relevant storage areas to assist IBM Service in diagnosing analysis processing.
Parent topic: Runtime Diagnostics