SUP_HiperDispatchCPUConfig

Description:

This check monitors the number of CPUs installed and HiperDispatch state of the system. On systems where HiperDispatch is disabled, this check provides a warning when the highest CPU ID of any CPU configured to this system is close to the maximum allowed (X'3F'). On systems where HiperDispatch is enabled, this check is always successful.

The system runs this check whenever any of the following occur:

IBM® Health Checker for z/OS® starts
HiperDispatch mode switch
A CPU is dynamically added to the system's configuration

Note that you can only add this check on z/OS releases that support CPU ids greater than X'3F' and hardware capable of supporting more than 64 CPUs.

Reason for check:

A system with HiperDispatch disabled can use CPU ID 0 through CPU ID X'3F'. For the system to use CPU IDs above X'3F', the system must have HiperDispatch enabled.

z/OS releases the check applies to:

z/OS V1R11 and above with APAR OA30476 installed running on z hardware capable of running with more than 64 CPUs.

Type of check (local or remote):

Local

User override of IBM values:

The following sample shows the defaults for customizable values for this check. Use this sample to make permanent check customizations in an HZSPRMxx parmlib member used at IBM Health Checker for z/OS startup. If you just want a one-time only update to the check defaults, omit the first line (ADDREPLACE POLICY) and use the UPDATE statement on a MODIFY hzsproc command. Note that using non-POLICY UPDATEs in HZSPRMxx can lead to unexpected results and is therefore not recommended. End of change

ADDREPLACE POLICY[(policyname)] [STATEMENT(name)]
UPDATE
CHECK(IBMSUP, SUP_HiperDispatchCPUConfig)
ACTIVE
SEVERITY(LOW) 
INTERVAL(ONETIME) 
DATE('date_of_the_change')
PARM('CpusLeftB4NeedHd(8)')
REASON('Your reason for making the update.')

Debug support:

Verbose support:

Parameters accepted:

Yes, for a machine with HiperDispatch disabled. PARM('CpusLeftB4NeedHd(n)') specifies the minimum number of remaining CPUs which must be able to be installed and used with HiperDispatch disabled for the check to succeed. This value can be from 0 - 63. The default is 8. If you specify a value of 0 for this parameter, the check will never find an exception.

The system ignores this parameter when HiperDispatch is enabled.

Reference:

IEAOPTxx (OPT parameters) inz/OS MVS Initialization and Tuning Reference
Information on HiperDispatch mode in z/OS MVS Planning: Workload Management
SET command in z/OS MVS System Commands.

Messages:

This check issues the following exception messages:

IEAVEH081E

See the IEAVEH messages in z/OS MVS System Messages, Vol 6 (GOS-IEA).

SECLABEL recommended for multilevel security users:

SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for information on using SECLABELs.