GLYPH<SM590000> New IOCP Keyword MIXTYPE required for prior FICON$^{3}$ cards GLYPH<SM590000> New hardware (announced with Driver 36) GLYPH<SM590000> IOCP support for Dynamic I/O for standalone CF (Driver 36) GLYPH<SM590000> IBM Z Input/Output Configuration Program User’s Guide for ICP IOCP , SB10-7163 GLYPH<SM590000> IBM Z Stand-Alone Input/Output Configuration Program User's Guide , SB10-7166 GLYPH<SM590000> If an LPAR is defined at IPL with more than 64 logical processors, the LPAR automatically  operates in HiperDispatch Management Mode, regardless of the  HIPERDISPATCH= specification. GLYPH<SM590000> If logical processors are added to an LPAR that has 64 or fewer logical processors and the  extra logical processors raise the number of logical processors to more than 64, the LPAR  automatically operates in HiperDispatch Management Mode, regardless of the  HIPERDISPATCH=YES/NO  specification. That is, even if the LPAR has the  HIPERDISPATCH=NO specification, that LPAR is converted to operate in HiperDispatch Management Mode. GLYPH<SM590000> An LPAR with more than 64 logical processors that are running in HiperDispatch  Management Mode cannot be reverted to run in non-HiperDispatch Management Mode. 3 FICON Express16S+ does not allow a mixture of CHPID types on new cards Chapter 7. Operating system support  265 HiperDispatch 7.4.2 Base CPC features and functions IOCP required level for z14 servers:  The required level of IOCP for the z14 is IOCP 5.4.0  with PTFs. For more information, see the following publications: Dynamic Partition Manager V3.2:  At the time of this writing, the Dynamic Partition  Manager V3.2 is available for managing IBM Z servers that are running Linux. DPM 3.2 is  available with HMC Driver Level 36. IOCP does not need to configure a server that is  running in DPM mode. For more information, see  IBM Dynamic Partition Manager (DPM)  Guide , SB10-7170-02. In this section, we describe the features and functions of Base CPC. The  HIPERDISPATCH=YES/NO  parameter in the IEAOPTxx member of SYS1.PARMLIB and on  the  SET OPT=xx  command controls whether HiperDispatch is enabled or disabled for a z/OS  image. It can be changed dynamically, without an IPL or any outage. The default is that HiperDispatch is disabled on all releases, from z/OS V1R10 (which  requires PTFs for zIIP support) through z/OS V1R12. Beginning with z/OS V1R13, the IEAOPTxx keyword  HIPERDISPATCH  defaults to  YES  when it is  running on a z14, z13, z13s, zEC12, or zBC12 server. If  HIPERDISPATCH=NO  is specified, the  specification is accepted as it was on previous z/OS releases. The use of SMT on z14 servers requires that HiperDispatch is enabled on the operating  system. For more information, see “Simultaneous multithreading” on page 268. Additionally, with z/OS V1R12 or later, any LPAR that is running with more than 64 logical  processors is required to operate in HiperDispatch Management Mode. The following rules control this environment: