How to change the Health Checker IDMS_CPU_EFFECTIVENESS value?

Article Id: 51683
Status: Published
Updated On: 21-03-2018 06:14
Legacy Id: TEC520398
Products:
CA IDMS , CA IDMS - Database , CA IDMS - ADS
Issue/Introduction:

Description

After applying RO12080: ADD HEALTH CHECKS TO RELEASE 17.0, IDMS might show this new message:

DC285905 CPU effectiveness nn% for this interval is inadequate.

How could you change this CPU effectiveness value in the IBM Health Checker.

You can display current settings by; please note the default setting is CPURATIO(90):

F hzsproc,DISPLAY CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS*),DETAIL

Output looks like this:

 HZS0201I 05.16.29 CHECK DETAIL     987                           
 CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS?IDMSSYST)                   
  STATE: ACTIVE(ENABLED)             STATUS: EXCEPTION-HIGH       
  LAST RAN: 03/10/2010 05:08    NEXT SCHEDULED: 03/10/2010 05:23  
  INTERVAL: 0:15                                                  
  EXCEPTION INTERVAL: SYSTEM                                      
  SEVERITY: HIGH                                                  
  WTOTYPE: CRITICAL EVENTUAL ACTION                               
  SYSTEM DESCCODE: 11                                             
  DEFAULT PARAMETERS:       CPURATIO(90)                          
  REASON FOR CHECK:  Calculate the ratio of CPU time received     
                     versus CPU time required to provide a measure
                    of involuntary waits for CPU time. 
  MODIFIED BY: N/A                                      
  DEFAULT DATE: 20091008                                
  ORIGIN: HZSADDCK                                      
  LOCALE: REMOTE                                        
  DEBUG MODE: OFF  VERBOSE MODE: NO

Solution

Refer to the IBM documentation "Setting Up IBM Health Checker for z/OS" in the IBM Health Checker for z/OS User's Guide for more information.

CA IDMS PTF RO12080 implements the Health Checker code for IDMS release 17.0, indicating that CA IDMS now exploits the IBM Health Checker Facility. Each Health Check issues its output as messages, which you can view using SDSF, the HZSPRINT utility, or a log stream that collects a history of check output.

Assuming you want to permanently change or temporarily update the CA IDMS health checks IDMS_CPU_EFFECTIVENESS from CPURATIO(90) to (80):

These steps are also documented in the IBM Health Checker for z/OS User's Guide (SA22-7994-nn) and are not specific to CA IDMS.

Add member SYS1.PARMLIB(HZSPRM00) with the following statement:

ADDREPLACE POLICY STMT(UPD1) UPDATE CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS*) PARM='CPURATIO(80)' DATE(yyyymmdd)

In order to put the HZSPRMxx changes into effect, you either need to recycle the health checker address space or issue:

F hzsproc,REPLACE,PARMLIB=(00)

This will only change new instances of the check being added.

To update any currently active checks, issue command:

F hzsproc,UPDATE,CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS*),PARM='CPURATIO(80)'

Note: Certain system privileges are required to issue the Health Checker commands and to update the SYS1.PARMLIB members. See IBM Health Checker for z/OS User's Guide, 1.2.5 Create security definitions.

References:

IBM Health Checker for z/OS User's Guide (SA22-7994-nn) http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/E0Z2L111/CCONTENTS?DT=20070117140903.

RO12080: ADD HEALTH CHECKS TO RELEASE 17.0

RI05071: CA HEALTH CHECKER COMMON SERVICE NOW AVAILABLE (z/OS r11 SP8)

Environment:

Release:
Component: IDMS