ID

ID is an optional statement that can specify the following information:

Identification information printed in the heading of IOCP configuration reports on the ID1 and ID2 lines. See IOCP configuration reports for examples of the headings used on the reports.
Data set name for each IOCDS that appears on the Input/Output Configuration window of the Support Element for a CPC
Set of machine limits and rules to be enforced by IOCP when processing the I/O configuration
Name of the local system.

When specified, the ID statement must precede all RESOURCE, CHPID, CNTLUNIT, IODEVICE, UUID, and FUNCTION statements in the input stream. Also, when specified, it must include at least one keyword (for example, MSG1, MSG2, or SYSTEM). The ID statement can be specified only once in the input file. The ID statement parameters can appear in any order but you must code at least one parameter. If you do not specify the ID statement, no identifying information is printed on the ID1 and ID2 lines of the report headings.

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 ID statement is as follows:

[symbol]   ID    {MSG1='message'}
                 {MSG2='message'}
                 {SYSTEM=(processor[,number])}
                 {LSYSTEM=name}
                 {TOK=token}

MSG1=

Specifies the identification information that is printed on the ID1 line of the heading on IOCP configuration reports. The Support Element also uses the first eight characters of MSG1= (bytes 1-8) as the customer name for the IOCDS that appears on the Input/Output Configuration window of the Support Element for CPCs.

MSG2=

Specifies the identification information that is printed on the ID2 line of the heading on IOCP configuration reports.

'message'

Specifies a string of 1-64 characters of identification information. IOCP accepts any character in the string. Any incorrect character is translated to a quotation mark. See the "English (U.S.) I/O Interface Code" table for EBCDIC characters in 3270 IDS Character Set Reference for a list of valid printable characters. You must enclose the string within single quotation marks. Two consecutive single quotation marks are counted as one character and indicate a single quotation mark within the string (such as, MSG1='John''s I/O Report').

SYSTEM=

Specifies the machine limits and rules that IOCP enforces for verification of the IOCP input or when writing an IOCDS in preparation of a CPC upgrade. The stand-alone version of IOCP ignores the SYSTEM keyword. It is also ignored when IOCP is writing an IOCDS using keyword CHECKCPC=YES in the PARM parameter of the EXEC statement (z/OS or z/VSE) or CMS option CHECKCPC. In both cases, IOCP uses the machine limits and rules for the CPC on which IOCP is currently running.

When IOCP is writing an IOCDS in preparation of a CPC upgrade (keyword CHECKCPC=NO or option NOCHKCPC is specified), IOCP uses the machine limits and rules based on the SYSTEM keyword. IOCP requires the SYSTEM keyword when CHECKCPC=NO or NOCHKCPC is specified.

If the SYSTEM keyword is not specified and ICP IOCP runs on a CPC that it supports, IOCP uses the machine limits for that CPC. If the SYSTEM keyword is not specified and ICP IOCP runs on an unsupported CPC, IOCP uses default machine limits. See Table 1 for the default SYSTEM value.

See Machine limits and rules for a complete list of valid SYSTEM keyword values and their associated machine limits and rules.

processor

Specifies the machine type number of the target CPC for which the IOCP input is to be verified. For example, specify SYSTEM=(8561) if the IOCP input you need verified is for an 8561 CPC.

number

Specifies the machine limits number associated with the target CPC machine type for which the IOCP input is to be verified. Specify a single decimal number. The default value is the lowest number supported for the specified CPC machine type. For example, the default machine limits number for an 8561 is one.

LSYSTEM=name

Specifies the name of the local system. The name is a 1-8 alphanumeric (0-9, A-Z) name. IOCP requires the LSYSTEM keyword when CIB, CL5, CL6, and CS5 channel paths are defined. The CPC uses the local system name to identify itself when establishing a coupling facility connection using CIB, CL5, CL6, and CS5 channel paths. It is helpful to use the same CPC name specified on the Hardware Management Console.

TOK=token

Configuration programs use this keyword to pass to the CPC information required to enable the dynamic I/O configuration capability of any resulting IOCDS. This keyword is not intended for direct IOCP user input. It is mentioned here to inform you that IOCP accepts the keyword and the generated value.

Some CPCs have a fixed storage size for the Hardware System Area (HSA). These CPCs require every IOCDS to have a token. If the TOK keyword is not specified, IOCP generates a token of its own and, even though the Hardware Management Console might indicate dynamic I/O is enabled, no operating system supports dynamic I/O configuration. See Table 1 to determine if your CPC has fixed HSA.

For HCD: Do not alter an IOCP input file generated by HCD and use it to write an IOCDS. If changes are necessary, use HCD to regenerate the IOCP input.