IEAVEH071E    HiperDispatch is expected to be expected but it is actual

Explanation

Check SUP_HIPERDISPATCH determined the check's expected HiperDispatch state does not match the actual HiperDispatch state of the system. This system supports enabling HiperDispatch to increase system performance.

With HiperDispatch enabled, the system cache is utilized more efficiently and the system performance is improved in many configurations. The performance gain HiperDispatch provides typically increases with a newer hardware generation and can improve with newer releases of z/OS®.

With HiperDispatch disabled, the system cache is utilized less efficiently and does not receive the performance benefits provided by HiperDispatch.

On any z/OS release running on IBM® System z10® hardware, HiperDispatch disabled is the default. On IBM System z10, customers are encouraged to try running with HiperDispatch enabled.

Beginning with z/OS V1R13 on zEnterprise® 196 hardware, HiperDispatch enabled is the default. With zEnterprise 196 hardware, z/OS partitions with share greater than two physical processors will typically experience improved processor efficiency with HiperDispatch enabled.

IBM recommends that all partitions that see improved or equivalent processor efficiency with HiperDispatch enabled run with HiperDispatch enabled.

In the message text:
expected
HiperDispatch's expected state (enabled or disabled)
actual
HiperDispatch's actual state (enabled or disabled)

System action

The system continues to run in its current HiperDispatch state.

Operator response

Report this problem to the system programmer.

System programmer response

Prior to enabling HiperDispatch for the first time, review the "Planning Considerations for HiperDispatch Mode" White Paper located on IBM Techdocs at http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101229.

To address the exception from IEAVEH071E, do one of the following:
  1. Make the actual machine's HiperDispatch state equivalent to the check's expected HiperDispatch state by enabling or disabling HiperDispatch on the machine. Do this by updating the IEAOPTxx parmlib member to specify HIPERDISPATCH=YES or HIPERDISPATCH=NO.
  2. Update the check's expected HiperDispatch state to be consistent with the actual HiperDispatch state of the machine by supplying a check parameter of HIPERDISPATCH(YES) or HIPERDISPATCH(NO).
  3. When the machine is not a IBM System z10 and HIPERDISPATCH(NO) is specified, make sure that the MachTypes list includes the machine type where the partition runs.
  4. Rerun this Health Check.

Problem determination

N/A

Source

Supervisor Control

Module

IEAVEHCK,IEAVEHMS

Routing code

See note 35.

Descriptor code

12 is the default set by this check. See note 1.

Automation

N/A

Reference Documentation

"IEAOPTxx (OPT) Parameters" in z/OS MVS Initialization and Tuning Reference .

"SET Command" in z/OS MVS System Commands.

"Planning Considerations for HiperDispatch Mode" White Paper located on IBM Techdocs at http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101229

Parent topic: IEAVEH messages