Remove commands or logic that start or restart Runtime Diagnostics

Description

In z/OS V2R3, the command to start Runtime Diagnostics is added to the IBM-supplied parmlib member IEACMD00. As a result, Runtime Diagnostics is started automatically during system initialization, when you include the SYS1.IBM.PARMLIB data set in your parmlib concatenation. This change means that it is no longer necessary for you to explicitly start Runtime Diagnostics after each system IPL, whether through the COMMNDxx parmlib member, an automation program, or an operator command entered manually at the console.

For example, in previous releases, you might have placed the start command in your COMMNDxx parmlib member, as follows: 
COM='S HZR,SUB=MSTR'

As in previous releases, the Runtime Diagnostics address space (HZR) continues to run as an address space under the master subsystem and remains active until you stop it with the STOP command.

Tip: IBM recommends that you allow the HZR address space to be classified into the SYSSTC service class, or place it into an importance 1 single period service class with a high velocity goal.
This table provides more details about the migration action. Use this information to plan your changes to the system.
Element or feature: BCP
When change was introduced: z/OS V2R3.
Applies to migration from: z/OS V2R2 and z/OS V2R1.
Timing: Before the first IPL of z/OS V2R3.
Is the migration action required? Yes, if you have any system automation that starts or restarts Runtime Diagnostics.
Target system hardware requirements: None.
Target system software requirements: None.
Other system (coexistence or fallback) requirements: None.
Restrictions: None.
System impacts:
If you leave an automated START command for Runtime Diagnostics in place, the following message is issued when the system processes the IBM-supplied START command in IEACMD00: 
HZR0111I RUNTIME DIAGNOSTICS IS ALREADY ACTIVE
If your installation does not define a user ID for the HZR started task or a profile for HZR in the STARTED class with that user ID, the following message is issued when Runtime Diagnostics is started automatically during IPL: 
IRR813I NO PROFILE WAS FOUND IN THE 
STARTED CLASS FOR HZR WITH JOBNAME 
HZR. RACF WILL USE ICHRIN03.
Related IBM® Health Checker for z/OS® check: None.

Steps to take

Follow these steps:
  1. Remove commands or logic that start Runtime Diagnostics from automation programs or the COMMNDxx parmlib member. For example, remove the statement COM='S HZR,SUB=MSTR' from the COMMNDxx parmlib member, if specified.
  2. If your installation changed the Runtime Diagnostics default job name in SYS.PROCLIB, update the START command in IEACMD00 to associate the installation defined name with the default job name HZR. For example, if you changed the Runtime Diagnostics job name from HZR to HZRNEW, change the command in IEACMD00 from:
    COM='S HZR,SUB=MSTR'
    to:
    COM='S HZRNEW,SUB=MSTR,JOBNAME=HZR'
  3. When Runtime Diagnostics is started, the following message might be issued if the STARTED class is active. While this message is not a change to Runtime Diagnostics processing, the message might be new to you: 
    IRR813I NO PROFILE WAS FOUND IN THE STARTED CLASS FOR HZR WITH JOBNAME HZR. RACF WILL USE ICHRIN03.
    If you receive this message, one of the following problems has occurred:
    • The STARTED class has the RACLIST option, but no SAF profile exists for Runtime Diagnostics (HZR)
    • A SAF profile is defined for HZR, but the STARTED class is not RACLIST enabled
    • A SAF profile is defined for HZR, but the STARTED class was not refreshed so that the changes could take effect.
    • The RACLIST profile is not enabled on the system.
    In response, RACF uses the information in the started procedures table (ICHRIN03) to assign security information for HZR . Either ensure that the proper definition exists in the ICHRIN03 for HZR, or take one of the following actions:
    • Define a SAF profile for HZR in the STARTED class, as described in z/OS Problem Management.
    • Ensure that the STARTED class has the RACLIST option. For example:
      SETROPTS RACLIST(STARTED)
    • Refresh the STARTED class. For example: 
      SETROPTS RACLIST(STARTED) REFRESH

    If you have a security profile set up for Runtime Diagnostics (HZR) in the STARTED class before IPL, message IRR8131 is not issued. Security for Runtime Diagnostics works as it did in previous releases.

Reference information

For more information, see z/OS Problem Management.