Specifications

Chapter 3. z/OS notes 47
3.15 Health Checker
The z/OS Health Checker has been included in recent AD-CD releases, but may not be
configured for operation. A quick configuration (z/OS 1.12) involves the following steps; later
z/OS releases may use similar steps if the Health Checker is not already configured:
򐂰 Edit SYS1.SAMPLIB(HZSALLCP) and change the DSN operand (in the DD statement) to
something like DSN=SYS1.ADCD.HZSPDATA. A VOL=SER= parameter may be added
although the data set involved is not very large. Complete the JOB statement and run this
job.
򐂰 Create this member in a PROCLIB, such as USER.PROCLIB:
//HZSPROC PROC HZSPRM=’00’
//HZSSTEP EXEC PGM=HZSINIT,REGION=0K,TIME=NOLIMIT,
// PARM=’SET PARMLIB=&HZSPRM’
//HZSDATA DD DISP=OLD,DSN=SYS1.ADCD.HZSPDATA
򐂰 Edit ADCD PARMLIB member ISFPRM00 and add a CK parameter to the list of
authorizations allowed for systems programmers. (Remember the comma!)
򐂰 Enter the following commands in the ISPF option 6 display:
RDEFINE XFACILIT HZS.* UACC(READ)
SETROPTS RACLIST(XFACILIT) REFRESH
RDEFINE STARTED HZSPROC STDATA(USER(START1) GROUP(SYS1) TRUSTED(YES))
SETROPTS RACLIST(STARTED) REFRESH
򐂰 From the MVS operator console, stop the SDSF server (P SDSF) and start it again (S SDSF).
򐂰 From the MVS operator console, start the Health Checker (S HZSPROC). This will probably
produce considerable output on the MVS console. It can be ignored unless there is an
obvious error message about the HZSPROC start.
򐂰 Go to the SDSF primary panel and enter the CK command. This should display output from
the Health Checker.
򐂰 Remember to stop it (P HZSPROC) when stopping z/OS. You might add the stop
command to the SHUTDOWN scripts in the ADCD PARMLIB.
3.16 RMF-III
Recent releases of the AD system may not start RMF-III correctly, with a failure finding a
module. This can be corrected by adding GDDM®.SADMMOD to the link list. (Consider
adding it to all the PRODxx members in PARMLIB.)
3.17 Compressing PARMLIB
We typically make many PARMLIB changes (usually to the current ADCD PARMLIB) while
adjusting the AD system to our individual needs.
14
We then need to compress PARMLIB to
recover space and prevent unexpected expansion into multiple extents. With recent AD-CD
releases, a simple compress (using the Z option in the ISPF 3.4 panel) fails because the
PARMIB is being used by another job. Pressing PF1 twice (when this error message is
14
This is not a good practice, but it is very common. A better method is to (1) copy the target PARMLIB member to
USER.PARMLIB, and (2) make the changes there. USER.PARMLIB is concatenated before the normal ADCD
PARML IB.