RESOURCE

Edit online
RESOURCE is a required statement that defines:
  • Logical partition names
  • Multiple Image Facility (MIF) image ID numbers assigned to the logical partitions
  • Logical channel subsystems (CSSs)
  • The maximum number of devices that can be dynamically defined for a dynamic-capable IOCDS
  • Reserved logical partitions, for a dynamic-capable IOCDS.
The RESOURCE statement must:
  • Appear only once in an IOCP input file
  • Follow the ID statement (if specified)
  • Precede all CHPID, CNTLUNIT, IODEVICE, UUID, and FUNCTION statements
  • Include every logical partition in the configuration
  • Have either the PART or PARTITION parameter specified.

If the RESOURCE statement is not specified or is in error, IOCP terminates all processing and does not validate the remaining IOCP statements.

See Coding IOCP statements for a summary of the rules for coding statements and the notation used in this document to illustrate statements.

The format of the RESOURCE statement is as follows: 
[symbol]     RESOURCE   PART|PARTITION=((CSS(cssid),{name|({name|*}
                            [,MIF image ID])},...),...)
                        [MAXDEV=((CSS(cssid),ss[,ss][,ss]),...)]
PART=
PARTITION=
Specifies the logical partitions (LPs) in the configuration. You can use either form.
cssid
Specifies the logical channel subsystem (CSS) ID to define. The CSS ID is a 1-digit number in the range 0-n. See Table 2 to determine the maximum CSS ID your CPC supports.

All the logical partitions following a CSS ID parameter are defined in the CSS. You can define as many CSSs as your CPC supports.

If you are defining only CSS 0, the CSS parameter is optional. Also, if you are defining only a single CSS, the PART or PARTITION parameter can be enclosed in a single set of parentheses. For example: 
PART=(CSS(1),LP1)
For a CPC with a fixed HSA storage size, IOCP defines any missing CSS so that every CSS your CPC supports is defined. See Table 1 to determine if your CPC has fixed HSA.
If you are defining the Licensed Machine Code (LMC) partition MCS_1, it must be defined in the last CSS supported by your CPC. See Table 1 to determine if your CPC supports the MCS_1 partition.
name
Specifies the name of the logical partition (LP) to be defined. The LP name is a 1-8 alphanumeric (0-9, A-Z) character name that must have a nonnumeric first character.

The words PHYSICAL, REC, SYSTEM, and PRIMnnnn (where nnnn is a 4-digit decimal number) are reserved and cannot be used as the names of LPs.

Some CPCs support the definition of a special LMC partition named MCS_1 (also known as a firmware partition). The MCS_1 partition can be defined on a stand-alone coupling facility (CF) CPC so dynamic I/O changes can be made to it by using HCD from another CPC. Note that the CPC must power-on reset with an IOCDS containing the MCS_1 partition before dynamic I/O changes can be made to the CPC. The CPC using HCD does not require the MCS_1 partition be defined on it. Also, the MCS_1 partition cannot contain any I/O resources (for example, channel paths or functions) and UUID checking cannot be enabled for it. See Table 1 to determine if your CPC allows the MCS_1 partition be specified on the RESOURCE statement or if MCS_1 is optional for your CPC but always in the IOCDS.
Some CPCs support dynamic I/O changes being made to a stand-alone CF CPC without the definition of the MCS_1 partition and IOCP rejects the specification of MCS_1. To determine if your CPC supports dynamic I/O for a stand-alone CF CPC without the specification of MCS_1, see Table 1.
Beginning with IBM z16 and IBM LinuxONE 4 CPCs in non-DPM mode (machine types 3931 and 3932) at firmware Driver 51 MCL Bundle S25, the target CPC for dynamic I/O changes can be hosting Linux on IBM Z and/or z/TPF images and does not need to be a stand-alone CF CPC. Note that making dynamic I/O changes in this fashion to any CPC prior to this firmware level that is not a stand-alone CF is not supported. For more information, see Table 1.
You must specify all LPs in the configuration. However, for some CPCs the MCS_1 partition is optional and IOCP defines it if it is not specified (see Table 1 to determine if your CPC has MCS_1 as optional but always in the IOCDS). You can define up to 15 LPs in a CSS. Each LP name in the configuration must be unique. See Table 2 to determine the maximum number of LPs your CPC supports. Also see Table 1 to determine how many partitions your CPC supports in the maximum CSS ID for your CPC.

A logical partition specified on the RESOURCE statement can exist without any channel paths and functions assigned to it.

For z/OS: For coupling facility logical partitions (LPs), match the LP name specified in the PART or PARTITION keyword of the RESOURCE statement with the NAME keyword of the CF statement in the policy information defined for the coupling facility resource management (CFRM) policy of the site.

*
Specifies reserving an LP in the specified CSS with the specified MIF image ID. A reserved LP can be specified only for a dynamic-capable IOCDS (TOK keyword on ID statement). A dynamic-capable IOCDS is built when using HCD on z/OS or VM or when specifying IOCP CMS utility option DYN for VM. A dynamic-capable IOCDS is also built for CPCs that have a fixed HSA storage size. Space in the HSA is allocated for reserved LPs but cannot be used until a dynamic I/O configuration change is made to assign a name and other resources to the LP.
The following rules apply when specifying reserved LPs:
  • A reserved LP must have a user-specified MIF image ID.
  • A reserved LP cannot have any channel paths assigned to it.
  • An IOCDS cannot contain only reserved LPs.
  • At least one LP must be defined with a name.
For a CPC with fixed HSA, IOCP defines enough reserved LPs to ensure that the maximum number of LPs that your CPC supports is available in every CSS. See Table 1 to determine if your CPC has fixed HSA.
MIF image ID
Specifies the MIF (multiple image facility) image ID associated with a logical partition (LP). The MIF image ID is a 1-digit hexadecimal number in the range 1-F (see note 8). You can specify the MIF image IDs non-consecutively in any order. MIF image IDs must be unique within a CSS but can be duplicated in different CSSs. If you are defining the LMC partition MCS_1, it must be defined with MIF image ID B or you may omit the MIF image ID and IOCP defaults to the correct value.

Shared channel paths used for ESCON CTC or FICON CTC communication require a MIF image ID. See the CUADD keyword CUADD=address for more information.

If you do not specify a MIF image ID for every LP, IOCP arbitrarily assigns MIF image IDs to the unassigned LPs.

The MIF image ID is different from the logical partition identifier (ID) displayed on the General page of the image profile for CPCs.

For z/OS: For coupling facility logical partitions (LPs), the partition ID specified on the activation profile for the CF image on the Support Element must match the number specified in the PARTITION keyword of the CF statement in the policy information defined for the coupling facility resource management (CFRM) policy of the site. It is helpful to specify a partition ID that is a concatenation of the CSS ID and MIF image ID. The MIF image ID is no longer used for this purpose.

MAXDEV=
Specifies the maximum number of devices, including those devices defined in the IOCDS, that can be dynamically added to the configuration. IOCP ignores the MAXDEV keyword for CPCs that have a fixed HSA storage size. For a CPC with fixed HSA, the maximum number of devices that are supported by your CPC are available. See Table 1 to determine if your CPC has fixed HSA.

If the MAXDEV keyword is specified, the IOCDS must be dynamic-capable (TOK keyword on ID statement). A dynamic-capable IOCDS is built when using HCD on z/OS or VM or when calling the IOCP CMS utility with privilege class B for VM.

If the MAXDEV keyword is not specified for a dynamic-capable IOCDS, IOCP defaults the maximum number of devices to the maximum the CPC supports for subchannel set 0 for each defined CSS. If you define devices in subchannel set 1 of any CSS, IOCP sets the default for the maximum number of devices for each subchannel set 1 with devices to the maximum the CPC supports. Otherwise, subchannel set 1 has a default value of zero.

If the MAXDEV keyword is specified for a dynamic-capable IOCDS but omits a defined CSS, IOCP sets the default for the maximum number of devices to the maximum the CPC supports for subchannel set 0 for the CSS. If you define devices in subchannel set 1 of the omitted CSS, IOCP sets the default for the maximum number of devices for subchannel set 1 to the maximum the CPC supports. Otherwise, subchannel set 1 has a default value of zero.

cssid
Specifies the logical channel subsystem (CSS) ID associated with this parameter. The CSS ID is a 1-digit number in the range of 0-n. See Table 2 to determine the maximum CSS ID your CPC supports.
The CSS ID must have been defined in the PART or PARTITION keyword on the RESOURCE statement. You can specify as many CSSs as you defined. If only a single CSS was defined, the CSS parameter is optional. Also, if you only specify a single CSS, the MAXDEV parameter can be enclosed in a single set of parentheses. For example: 
MAXDEV=(CSS(1),60K)
ss
Specifies the maximum number of devices, including those devices defined in the IOCDS, that can be used for dynamic I/O configuration in a subchannel set in a CSS. The first ss value defines the maximum number of devices for subchannel set 0 in a CSS. The second ss value defines the maximum number of devices for subchannel set 1 in the same CSS. See Table 2 to determine the number of subchannel sets your CPC supports. All CPCs support subchannel set 0.

To specify a value for subchannel set 1, you must also specify a value for subchannel set 0.

The format of ss is: 
{number | MIN | MAX}
number
Specifies the maximum number of devices, including those devices defined in the IOCDS, that can be used for dynamic I/O configuration in a subchannel set in a CSS. The number can be a 1- to 5-digit decimal number in the range 0-n. The n is the maximum number of devices your CPC supports for the subchannel set. The number can also be in the form nnK. The nn is a 1- or 2-digit decimal number that is multiplied by 1024 to get the maximum number of devices. (For example, 60K and 61440 are equivalent values.) See Table 2 to determine the maximum number of devices per subchannel set that your CPC supports. The configuration cannot contain more devices than the MAXDEV value.
MIN
Specifies that the maximum device value in the I/O configuration is equal to the number of devices defined in the IOCDS for the subchannel set in the CSS. Therefore, no new devices can be dynamically added to the I/O configuration for the subchannel set in the CSS unless other devices have been deleted.
MAX
Specifies that the maximum device value in the I/O configuration for the subchannel set in the CSS is equal to the maximum number of devices supported by your CPC for the subchannel set (see Table 2).