Start Runtime Diagnostics at system initialization

Description: Before z/OS V1R13, Runtime Diagnostics ran as a as a started task under the master subsystem and had to be started each time you wanted an analysis. It was started, did its analysis, then ended. Beginning with z/OS V1R13, you can start Runtime Diagnostics to run as an address space under the master subsystem. After you start the Runtime Diagnostics address space (HZR), it remains running until stopped using the STOP command. Use the MODIFY HZR,ANALYZE command to generate a Runtime Diagnostics analysis and report.

Element or feature:

BCP.

When change was introduced:

z/OS V1R13.

Applies to migration from:

z/OS V1R12.

Timing:

Before the first IPL of z/OS V2R1.

Is the migration action required?

No, but recommended to use Runtime Diagnostics.

Target system hardware requirements:

None.

Target system software requirements:

None.

Other system (coexistence or fallback) requirements:

None.

Restrictions:

None.

System impacts:

None.

Related IBM Health Checker for z/OS check:

None.

Steps to take: To start the Runtime Diagnostics address space (HZR) on z/OS V2R1:

Ensure the hzrproc (HZR) points to PGM=HZRINIT, not PGM=HZRIMAIN as in z/OS V1R12. The hzrproc (HZR) ships in the SYS1.PROCLIB data set.
If you want to start Runtime Diagnostics address space (HZR) during system initialization, specify COM='S HZR,SUB=MSTR' in the COMMNDxx parmlib member. Otherwise, the HZR address space must be started manually: S HZR,SUB=MSTR
After the Runtime Diagnostics address space (HZR) is started, use the MODIFY HZR,ANALYZE command to generate Runtime Diagnostics' reports.

Reference information: For complete details about using Runtime Diagnostics, see the topic "Runtime Diagnostics overview" in z/OS Problem Management.