Migration and exploitation considerations for z196 and z114 server functions

A WLM goal adjustment might be required when using HiperDispatch. Review and update your WLM policies as necessary.

To realize the benefits of HiperDispatch, z/OS has been changed to force HiperDispatch=YES for LPARs with greater than 64 CPUs. On LPARs with greater than 64 CPUs defined on a zEnterprise server with IEAOPTxx specifying HIPERDISPATCH=NO during IPL (or SET OPT=xx after IPL), the system generates a message but continues to run with HIPERDISPATCH=YES. The new message is IRA865I HIPERDISPATCH=YES FORCED DUE TO GREATER THAN 64 LPS DEFINED.

On LPARs in which HIPERDISPATCH=NO is specified with less than 64 CPUs, you can dynamically add more CPUs and continue to run in HIPERDISPATCH=NO. However, you may see the new message ISN012E HIPERDISPATCH MUST BE ENABLED TO CONFIGURE CPU IDS GREATER THAN 3F ONLINE.

Any attempt to configure CPUs greater than 64 CPUs online in HIPERDISPATCH=NO will be rejected with message IEE241I CPU(x) NOT RECONFIGURED ONLINE - REQUIRES HIPERDISPATCH ENABLED.

An LPAR with greater than 64 CPUs that dynamically changed to HIPERDISPATCH=YES cannot go back to HIPERDISPATCH=NO. It will be treated as if it was IPLed with HIPERDISPATCH=YES after HIPERDISPATCH=YES is activated.

The first subchannel set (SS 0) allows definitions of any type of device, such as bases, aliases, secondaries, and those other than disk that do not implement the concept of associated aliases or secondaries. The second and third subchannel sets (SS1 and SS2) can now both be designated for use for disk alias devices (of both primary and secondary devices), or Metro Mirror secondary devices only. The third subchannel set applies ESCON, FICON® and zHPF protocols. Definitions for the third subchannel set are similar to those for the second subchannel set and can be made with HCD.

The IODF statement of LOADxx allows users to indicate which devices to use during IPL (that is, devices that are connected to subchannel set 0, 1 or 2). This specification is done on the IODF statement (column 36). For more information, see z/OS MVS Initialization and Tuning Reference.

To IPL from an alternate subchannel set, you need to specify a 5 digit load address on the LPAR image profile on the HMC, and have the appropriate specification on the IODF statement column 36 in LOADxx. This capability is available for z196 as of September 2011 (GA2) and later and for z114. z114 supports only SS0 and SS1, so you cannot IPL from subchannel set 2 (SS2).

• Performance management
• Integrated private data network

If you are using the CPU Measurement Facility (Hardware Instrumentation Services), there is a new parameter on the MODIFY hisproc command. You can use this parameter, STATECHANGE, to override the default action to take when a CPU speed change is detected within the HIS component.

• ANSI X9.8 Pin security
• Enhanced Common Cryptographic Architecture (CCA), 64bit, CP Assist for Cryptographic Function (CPACF) enhancements
• Secure Keyed-Hash Message Authentication Code (HMAC)
• CKDS Constraint Relief
• PCI Audit, Elliptical Curve Cryptography (ECC) Digital Signature Algorithm
• CBC Key Wrap
• PKA RSA OEAP with SHA-256
• Expanded support for AES algorithm
• Enhanced ANSI TR-31 Secure Key Exchange
• PIN block decimalization table protection
• PKA RSA OAEP with SHA-256 algorithm, additional Elliptic Curve Cryptography (ECC) functions.

zDAC is designed to perform discovery for all systems in a sysplex that support the function. The proposed configuration will incorporate the current contents of the I/O definition file (IODF) with additions for newly installed and changed control units and devices. zDAC is designed to help simplify I/O configuration on CPC running z/OS and reduce complexity and setup time. zDAC applies to all FICON features supported on zEnterprise servers when configured as CHPID type FC, and is supported by z/OS V1R12 and later.

To use zDAC, you must first establish a policy for the discovery operation. This is done through HCD or HCM. You can limit the scope of the discovery, limit the proposal information, indicate the desired number of paths to discovered logical control units, and indicate the method used for device and control unit numbering. After controllers and devices are discovered, you can select which controllers to be defined and accept or override the proposed values for control units and devices.

• z/OS Sysplex Distributor traffic: Network traffic that is associated with a distributed Virtual Internet Protocol Address (VIPA) is assigned a unique input queue allowing the Sysplex Distributor traffic to be immediately distributed to the target host.
• z/OS bulk data traffic: Network traffic that is dynamically associated with a streaming (bulk data) TCP connection is assigned to a unique input queue allowing the bulk data processing to be assigned the appropriate resources and isolated from critical interactive workloads.

IWQ is supported on zEnterprise CPC and System z10, and is exclusive to OSA-Express3 CHPID types OSD and OSX (exclusive to zEnterprise CPC). There are some Communications Server configuration settings required to enable multiple inbound data queues.

Exploitation restriction. When programs exploit the ARCH(9) or TUNE(9) option, those programs can only run on zEnterprise servers, or an operation exception will occur. This is a consideration for programs that will run on different server levels (z10 and z9® servers) during development, test, and production, as well as during fallback or disaster recovery.