Machine rules

Table 1 lists the machine rules for the CPCs that IOCP supports.

Table 1. Machine rules
Machine rules	Machine type (See Note 1)
Machine rules	2817,1	2818,1	2827,1	2828,1	2964,1	2965,1	3906,1	3907,1	8561,1	8562,1	3931,1	3932,1	9175,1	9176,1
Write IOCDS in preparation for CPC upgrade (CHECKCPC=NO or NOCHKCPC)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
CPC has fixed HSA	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Default system if IOCP is running on an unsupported processor	No	No	No	No	No	No	No	No	No	No	No	No	Yes	No
FC and FCP PCHIDs on same adapter require MIXTYPE keyword	No	No	No	No	No	No	Yes	Yes	Yes	Yes	No (2)	No (2)	No (2)	No (2)
OSC and OSD PCHIDs defined on same adapter	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	No (5)	No (5)
MCS_1 partition allowed on RESOURCE statement	No	No	No	No	No	No	Yes (1)	Yes (1)	Yes	Yes	No	No	No	No
MCS_1 partition optional on RESOURCE statement but always in IOCDS	No	No	No	No	No	No	No	No	Yes	Yes	No	No	No	No
MCS_1 partition rejected on RESOURCE statement but dynamic I/O supported for remote CPC (3)	No	No	No	No	No	No	No	No	No	No	Yes (4)	Yes (4)	Yes	Yes
MCS_1 partition rejected on RESOURCE statement but dynamic I/O supported for stand-alone CF CPC	No	No	No	No	No	No	No	No	No	No	Yes	Yes	Yes	Yes
Notes: The LMC partition MCS_1 (also known as a firmware partition) is supported as follows: On 3907 and 3906 models at EC P41414 or later Both the CPC where MCS_1 is defined and the CPC performing the Hardware Only Dynamic I/O changes must be at an EC level that supports the MCS_1 partition. MCS_1 only needs to be defined on the stand-alone CF 3906 or 3907 CPC where the Hardware Only Dynamic I/O changes are targeted. The mixing of FC and FCP PCHIDs on the same adapter is not allowed with or without the MIXTYPE keyword. Dynamic I/O changes are supported for a remote CPC that hosts Linux on IBM Z and/or z/TPF images. The remote CPC must be in non-DPM (Dynamic Partition Manager) mode. Both the CPC initiating the dynamic I/O change and the remote target CPC must support this capability. Also, the initiating CPC must use z/OS release 2.4 or higher with APAR OA65559 installed. The 3931 and 3932 models support dynamic I/O changes for Linux on IBM Z and z/TPF beginning with firmware Driver 51 MCL Bundle S25. Networking adapters do not support the definition of both OSC and OSD PCHIDs on an adapter, but IOCP does not prevent this until the 9175 models. IOCP determines that channel paths are on the same adapter when their PCHIDs are in the same modulo-4 PCHID slot.

Note: See MIXTYPE for more information about the MIXTYPE keyword on the CHPID statement.

To write an IOCDS in preparation for a CPC upgrade, you specify keyword CHECKCPC=NO in the PARM parameter of the EXEC statement (z/OS® or VSE) or CMS option NOCHKCPC. To prepare for an upgrade, you can write an IOCDS to any CPC that requires the ICP version of IOCP. See Table 2 to determine which CPCs require an IOCDS written by ICP IOCP.

Note: IOCP can write an IOCDS in preparation for an upgrade to a CPC for which IBM® does not offer an upgrade. For example, you can write a SYSTEM=(8562,1) IOCDS to a 8561 CPC but no upgrade is offered from a 8561 to a 8562 and the IOCDS is unusable on the 8561.