How to get reports on the four IBM Health Checks issued by an IDMS CV?
Release: All supported releases
There are a variety of facilities to report results of Health Checks:
SDSF CK command
HZSPRINT Utility
Health Checker log stream
CA SYSVIEW
This document will show examples of how to look at Health Checker results using CA SYSVIEW and the IBM HZSPRINT utility.
The messages issued at CV startup will show you the checks that have been registered. Each of the four Health Checks described in RO12080 and in APPENDIX A of the 17.0 SP1 SYSTEMS OPERATIONS GUIDE will be appended with the SYSTEM ID of the IDMS system you run.
Example:
DC024000 V1700 T0 HEALTH CHECKER: Infrastructure initialized DC024000 V1700 T0 HEALTH CHECKER: Added check routine IDMS_SCRATCH_IN_MEMORY@SYST1700DC024000 V1700 T0 HEALTH CHECKER: Added check routine IDMS_CPU_EFFECTIVENESS@SYST1700DC024000 V1700 T0 HEALTH CHECKER: Added check routine IDMS_CHANGE_TRACKING@SYST1700DC024000 V1700 T0 HEALTH CHECKER: Added check routine IDMS_ZIIP_USAGE@SYST1700DC024000 V1700 T0 HEALTH CHECKER: All check routines registered
SYSVIEW:
From the main SYSVIEW menu, select "2 Menu MVS":
From the MVS menu select "12 MENU HCHECKER"
From the Health Checker menu select "1 HCOWNER"
From the HCOWNER screen, select CA_IDMS
Select any of the individual checks to see results.
Examples of running the batch utility HZSPRINT.
This utility accepts a parameter that is either the full CHECK_OWNER,CHECK_NAME or a wildcarded filter.
JCL to run the job is very simple.
Here is an example with the full owner and check name:
//HZSPRINT EXEC PGM=HZSPRNT,TIME=1440,REGION=0M,
// PARM=('CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST####)')
//SYSOUT DD SYSOUT=*,DCB=(LRECL=256)
This job produced the following output:
This job produced the following output: *************************************************************************
** HZSPRINT (HBB7750-07288) 2010/10/22 09:19 **
** HZSU001I Check messages **
** Sysplex: PLEXC1 System: CA31 **
** Filter: CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST####) **
************************************************************************* ************************************************************************* ** Start: CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST####) ** ************************************************************************* CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST1700)
START TIME: 10/20/2010 08:05:34.756345
CHECK DATE: 20091008 CHECK SEVERITY: MEDIUM
DC200024 CA IDMS Change Tracking is in use. Change tracking enables changing the database environment of a Central Version (CV) in a fault-tolerant manner. Specifically, it permits the DBA to perform the following dynamic actions:
If the CV fails, the runtime database definition is restored from SYSTRK files during restart, ensuring that the files being updated at the time of failure are the ones recovered by warmstart unless explicitly
overridden by changes in the JCL used to restart the CV.
END TIME: 10/20/2010 08:05:34.756572 STATUS: SUCCESSFUL ************************************************************************* ** End: CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST####) ** *************************************************************************
If you were to run this JCL with an '*' after the CHECK_NAME instead of the '@' and SystemID it would produce a report for ALL IDMS CVs that issued that check.
Example:
//HZSPRINT EXEC PGM=HZSPRNT,TIME=1440,REGION=0M,
// PARM=('CHECK(CA_IDMS,IDMS_ZIIP_USAGE*)')
//SYSOUT DD SYSOUT=*,DCB=(LRECL=256)
To see ALL checks issued by all IDMS CVs on the LPAR you can specify a single '*' for Check_name:
//HZSPRINT EXEC PGM=HZSPRNT,TIME=1440,REGION=0M,
// PARM=('CHECK(CA_IDMS,*)')
//SYSOUT DD SYSOUT=*,DCB=(LRECL=256)