- ARCHLVL
- The ARCHLVL statement specifies the mode in which the operating
system will run. In z/OS®, the
processor determines the appropriate z/OS architecture
mode, and you do not need to specify the ARCHLVL parameter. It is
recommended that you do not specify the ARCHLVL statement. Note: Specifying the ARCHLVL parameter explicitly identifies the nucleus extension, IEANUCax, for the architecture level of your system. The system will use this extension along with the common base, IEANUC0x, to build the nucleus.
Column Contents 1-7 ARCHLVL 10 A one-digit value to specify the architecture level for the nucleus extension. Default: 2 (run in z/Architecture® mode).Note: If you specify a value for ARCHLVL that is not the default for the processor, message IEA368I will be issued during the IPL process, and the value you specified will be ignored. - DYNCPADD
- Indicates if z/OS support
for dynamic CPU
/core
addition
is enabled. Column Contents 1-8 DYNCPADD 10-16 {nnnn | ENABLE | DISABLE} - nnnn
- specifies if dynamic CPU/core addition
functionality should be enabled such that nnnn CPUs/cores can be dynamically added
to the image for the life of the IPL. nnnn must
be a left-justified value without any leading zeros. Specifying 8
or 16 is acceptable syntax for nnnn; 16
is the default. The number of CPUs/cores that can be dynamically added will be the
minimum between:
- nnnn plus the highest CPU/core ID defined at IPL
- Highest CPU/core ID
that the machine supports
- Highest CPU/core ID
the z/OS release supports
If you specify nnnn, choose a value that is large enough to be able to dynamically add more CPUs
/cores than you could envision
for the life of the IPL, then add some extra and set that value in nnnn. - nnnn plus the highest CPU
- DISABLE
- Specifies if dynamic CPU/core addition
functionality should be disabled. If either the hardware or the z/OS release do not support dynamic
CPU/core addition, dynamic
CPU/core addition will
be disabled.
- ENABLE
- Specifies if dynamic CPU/core addition
functionality should be enabled. The hardware and the z/OS release must support dynamic CPU/core addition to be able to
dynamically add a CPU/core after
IPL. When you specify ENABLE, z/OS prepares
to dynamically add the smaller of the following:
- Highest CPU/core ID
the hardware supports
- Highest CPU/core ID
the z/OS release supports.
IBM® recommends specifying nnnn to avoid allocating CPU
/core-related
storage for CPUs/cores which
will never be dynamically added for the life of the IPL. - Highest CPU
Default: 16Note:When PROCVIEW CPU
is in effect, DYNCPADD applies to CPUs. When PROCVIEW CORE is in effect,
DYNCPADD applies to cores. - HWNAME
- Specifies the name of a central processor complex (CPC), as defined
to hardware configuration definition (HCD). The HWNAME parameter is
used as a filter to define value parameters for a specified processor.
This optional filter parameter identifies a segment of LOADxx that may contain LOADxx statements that will be used if the specified HWNAME matches the name of the processor where the LOADxx statement is running. When HWNAME is specified, it resets the LPARNAME and VMUSERID to their default values.Note: Before the specification of this keyword, all statements up to this keyword pertain to any CPC. This keyword cannot be reset, and all subsequent statements pertain to the last specified HWNAME.
Column Contents 1-6 HWNAME 10-17 A required hardware processor name as defined in the IODF. There is no default value. - IEASYM
- The IEASYM statement identifies one or more suffixes of IEASYMxx
members of SYS1.PARMLIB that take the following steps for one or more
systems:
- Define static system symbols.
- Specify the IEASYSxx parmlib members that the system is to use.
To specify one IEASYMxx parmlib member, code IEASYM as follows:Column Contents 1-6 IEASYM 10-11 A 2-character suffix appended to “IEASYM” to select the member. The following example shows an IEASYM statement that tells the system to use the IEASYM01 parmlib member:* *---+----1----+----2----+----3----+----4----+----5----+----6----+----7-- IEASYM 01 *To specify one IEASYMxx parmlib member and display a list of member names in message IEA009I, code IEASYM as follows:Column Contents 1-6 IEASYM 10 A left parenthesis. 11-12 A 2-character suffix appended to “IEASYM” to select the member. 13-14 The following characters: ,L 15 A right parenthesis. The following example shows an IEASYM statement that tells the system to use the IEASYM01 parmlib member and display the names of those members in message IEA009I.* *---+----1----+----2----+----3----+----4----+----5----+----6----+----7-- IEASYM (01,L) *To specify more than one IEASYMxx parmlib member, code IEASYM as follows:Column Contents 1-6 IEASYM 10 A left parenthesis. 11-71 A list of 2-character suffixes appended to IEASYM to select the members. To display a list of member names in message IEA009I, specify ,L anywhere after the first suffix and enclose the values in parentheses, as shown in the example below. The following example shows an IEASYM statement that tells the system to use the IEASYM01 and IEASYM02 parmlib members and display the names of those members in message IEA009I.* *---+----1----+----2----+----3----+----4----+----5----+----6----+----7-- IEASYM (01,02,L) *If you specify a list of IEASYMxx suffixes, the system processes them from left to right. The system uses the definitions in all IEASYMxx members for which suffixes are specified. If the system finds duplicate definitions, the last definition overrides any previous definitions.
Default: None. If you do not specify an IEASYM statement, the system does not process IEASYMxx during initialization.
- INITSQA
- The INITSQA statement allows additional SQA and ESQA storage to
be reserved for IPL and NIP processing when the default amount is
not sufficient. Note that increasing the minimum below the line SQA
allocation must be done with caution to ensure that it does not affect
the lower boundary of CSA storage. (See SQA for
more information about specifying SQA storage.) If a syntax error
exists, the entire statement is ignored and message IEA368I is issued.
Column Contents 1-7 INITSQA 10-14 The amount of SQA to be added to the default initial amount. If blank, no SQA is added. If non-blank, a 4-digit numeric value followed by a multiplier of K or M must be specified. Value Range: 0000 K to 2048 K or 0000 M to 0002 M
Default: 0000 K
16-20 The amount of ESQA to be added to the default initial amount. If blank, no ESQA is added. If non-blank, a 4-digit numeric value followed by a multiplier of K or M must be specified. Value Range: 0000 K to 8192 K or 0000 M to 0016 M
Default: 0000 K
- IODF
- The IODF statement identifies the I/O definition file that contains
information about the I/O configuration defined to your system through
the hardware configuration definition (HCD). To change the I/O configuration
definition when the system is running, use the activate process. For
information about the ACTIVATE command, see z/OS MVS System Commands.
For information about
using the HCD to change the I/O configuration definition, see z/OS HCD User's Guide.
Column Contents 1-4 IODF 10-11 IODF suffix. This suffix is appended to nnnnnnnn.IODF to form the name of the nnnnnnnn.IODFxx data set. Value Range: A two-digit hexadecimal number (X'00-FF'), asterisks ('**'), pluses ('++'), minuses ('--'), or equals ('==').
If you used HCD to create your I/O Configuration data set (IOCDS), you can specify asterisks, pluses, minuses, or equals for the IODF suffix. If you specify asterisks, pluses, minuses, or equals, z/OS uses the IODF name found in the hardware configuration token. This IODF represents the last I/O configuration in the channel subsystem which you activated during the last Power® On Reset (POR) or dynamic I/O configuration change. If you override descriptor fields 1 and 2 in the HCD panel with an invalid IODF name, z/OS treats IODF suffixes '**' and '++' as if no IODF suffix was specified in LOADxx (z/OS searches from X'00' to X'FF' for a production IODF). If an invalid IODF name is found and you specified '--', z/OS searches for a production IODF starting with a suffix of X'FF'and searches backwards to X'00'. If an invalid IODF name is found and '==' were specified, z/OS loads wait state X'0B1' reason code X'00B'.
If pluses ('++') are specified and a valid IODF name is found in the hardware token, but is not found in the search or cannot be used, IODF selection is made in the following order:- Search for the next available IODF starting with the current IODF suffix number plus one and search up to X'FF'. If none is found, the search continues from X'00' up to the current IODF number minus one.
- Select the first IODF that has both a processor definition in the IODF that matches the currently active hardware definition, and a matching operating system configuration identifier.
- If no matching IODF token is found, select the first IODF that has a matching operating system configuration identifier.
- If no matching operating system configuration identifier is found, a wait state is loaded.
If minuses ('--') are specified and a valid IODF name is found in the hardware token, but is not found in the search or cannot be used, IODF selection is made in the following order:- Search for the next available IODF starting with the current IODF suffix number minus one and search down to X'00' If none is found, the search continues from X'FF' down to the current number plus one.
- Select the first IODF that has both a processor definition in the IODF that matches the currently active hardware definition, and a matching operating system configuration identifier.
- If no matching IODF token is found, select the first IODF that has a matching operating system configuration identifier.
- If no matching operating system configuration identifier is found, a wait state is loaded.
Default: If not specified, all possible IODFs (00-FF) are searched. The IODF selection is made in the following order:- If no matching IODF token is found, select the first IODF that has a matching operating system configuration identifier.
- If no matching operating system configuration identifier is found, a wait state is loaded.
Attention: If you specify asterisks ('**'), pluses ('++'), minuses ('--'), or equals ('==') for an IODF that does not reside on the IODF volume, or if you omit the IODF parameter altogether, the resulting search can substantially increase the time it takes to IPL the system, especially if the IODF volume has a large VTOC. In this situation, the system enters a X'073' wait state, indicating that the IPL is waiting for an I/O interrupt. To correct the problem, either specify the correct IODF suffix in LOADxx, or move the required IODF to the IODF volume, then reIPL.13-20 High-level qualifier for the IODF data set name. This qualifier is added to IODFxx to form the name of the nnnnnnnn.IODFxx data set. If equals ('========') are specified, z/OS attempts to extract the high-level qualifier from the hardware configuration token. If the token is not available, a wait state is loaded. Otherwise, z/OS uses this high-level qualifier for the IODF name. If the first character of the high-level qualifier found in the hardware configuration token is blanks (' '), a wait state is loaded.
Value Range: 1 to 8 alphameric characters or "========".
Default: If LOADxx resides in a SYSn.IPLPARM data set, and there is no high-level qualifier specified, the high-level qualifier defaults to the high-level qualifier of the SYSn.IPLPARM data set. If LOADxx resides in a SYS1.PARMLIB data set, and there is no high-level qualifier specified, a wait state is loaded.
22-29 Operating system configuration identifier. This eight-character identifier is used to select the appropriate configuration from those configurations defined in the IODF. For a list of eligible operating system configurations, select the “Define Operating System Configurations” option on the primary HCD panel. Default: If there is only one operating system configuration identifier in nnnnnnnn.IODFxx, then that one will be used. If there is more than one identifier and the identifier is not specified, a wait state is loaded.
31-32 Eligible device table identifier Default: 00
34 To indicate that the system should load all of the device support modules for the devices defined in the IODF and all the device types that support dynamic processing, specify either Y or blank. To indicate that the system should load only the modules required for the devices defined in your IODF, specify any non-blank character other than Y. Default: Y
36 Subchannel set indicator. Indicates the subchannel set IOS uses for normal base devices that have a special secondary device with the same address. The following values can be specified: - 0
- Indicates the normal base devices in subchannel set 0 are used for the IPL.
- n
- Indicates the special secondary devices in this subchannel set
are used for the IPL.
- *
- Indicates the subchannel set of the IPL device is used for the IPL.
If you are using a product to manage disk replication with HyperSwap® capability (for example, GDPS® or TPC-R), it is possible to have secondary devices attached to a subchannel set other than 0. Using such a configuration creates "special" pairs of devices consisting of one device in subchannel set 0 and a second device in an alternate subchannel set. Attaching secondary devices in an alternate subchannel set allows you to better utilize subchannel set 0 for devices that must be online and available for allocation.
You must provide direction when an IPL is required so
that z/OS brings the correct
devices online when HyperSwap occurs
(that is, when secondary devices become the devices in use, or in
other words, the "active" subchannel set for a special pair of devices
becomes the subchannel set to which the secondary devices are attached). On
systems where special secondary devices are connected, if this value
is not specified or is not valid (for example, not a 0, 1, 2, or *), the system will prompt the operator with
message IEA111D to determine what subchannel set should be used.Specifying '*' allows z/OS to
inherit the "active" subchannel set from the IPL devices (for IBM zEnterprise® 196 (z196) or later processors).
Specifying a number indicates that a specific subchannel set is to
be used as the "active" subchannel set. Consult the documentation
for your disk replication manager to determine whether special pairs
are supported and if any restrictions exist before specifying this
parameter.Default: None
- LPARNAME
- Specifies the name of a logical partition that is defined to a
processor, which is one of the following:
- The partition name specified on the “Add Partition” panel in HCD (see z/OS HCD User's Guide for more information).
- The partition name specified on the RESOURCE or CHPID statement that is input to the I/O configuration program (IOCP).
This optional filter parameter identifies a segment of LOADxx that may contain LOADxx statements that will be used if the specified HWNAME matches the name of the processor and the specified LPARNAME matches the actual LPAR logical partition in which z/OS is executing. When LPARNAME is specified, it resets VMUSERID to its default value. The LPARNAME parameter is used as a filter to define value parameters for a specified partition of a processor.Note: If running under z/VM®, you cannot filter using LPARNAME.Column Contents 1-8 LPARNAME 10-17 A required logical partition name as defined to LPAR. A blank entry indicates a z/OS image not running in LPAR mode. The default of matching the system being IPLed is set indirectly by specifying the HWNAME parameter. - MACHMIG
- Identifies one or more facilities that you do not want z/OS to use at this time because
migration to another processor, z/OS release,
or both is underway. Code the MACHMIG statement as follows:
Column Contents 1-7 MACHMIG 10-72 A list of facilities not to use. When more than one facility is listed, separate each from the previous by one or more blanks or commas. The following facilities can be specified in upper, lower, or mixed case: - EDAT2 (the hardware-based enhanced-DAT facility 2)
- TX (the hardware-based transactional-execution facility)
- RI (a hardware-based facility that is reserved for IBM use only)
- VEF (the hardware-based vector extension facility)
Example: The following example shows a MACHMIG statement that tells the system not to use the transactional execution facility and the enhanced DAT facility 2.* *---+----1----+----2----+----3----+----4----+----5----+----6----+----7-- MACHMIG TX,EDAT2 *Default: None. If you do not specify a MACHMIG statement, the system does not limit its exploitation of machine facilities.
- MTLSHARE
- The MTLSHARE statement enables a full-support MTL system to treat
manual tape library defined devices as stand-alone devices when the
Y(es) parameter is specified. Specifying Y also implies that the
cartridge loader on MTL defined devices should not be indexed. For
complete details please see z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries.
Column Contents 1-8 MTLSHARE 10 Y indicates that the system is to run in its coexistence mode, that is, treat MTL defined tape drives as stand-alone drives, and do not index the cartridge loaders on such drives. N indicates that the system is to run in its full function mode. MTL defined drives are treated as MTL resident drives, and cartridge loaders on such drives are indexed per MTL rules.
Default: N
- NUCLEUS
- The NUCLEUS statement identifies the IEANUC0x member of SYS1.NUCLEUS
that your system is to use. If the operator specified a nucleus identifier
on the LOAD parameter, z/OS ignores
the NUCLEUS statement.
Column Contents 1-7 NUCLEUS 10 A one-digit suffix that is appended to “IEANUC0” to select a member of SYS1.NUCLEUS. Default: 1Note: When you specify an alternate nucleus, the proper architectural extension of the nucleus must also exist. See page ARCHLVL for information about architectural extensions to the nucleus. - NUCLST
- The NUCLST statement:
- Identifies the NUCLSTxx parmlib member that your system is to use.
- Specifies whether the system is to load a wait state if any of the INCLUDE statements in the NUCLSTxx member specify a member that cannot be found in SYS1.NUCLEUS.
The NUCLSTxx member must reside in the same data set as the LOADxx member. For information about coding the NUCLSTxx member, see NUCLSTxx (customizing the nucleus region).Column Contents 1-6 NUCLST 10-11 A two-character suffix appended to “NUCLST” to select a NUCLST member. Default: None
13 The character ‘Y’ indicates that a wait state is to be loaded if any of the INCLUDE statements in the NUCLSTxx member specify a member that cannot be found in SYS1.NUCLEUS. If any other character is specified, the system does not load a wait state. Note: Uppercase ‘Y’ is required. Lowercase ‘y’ indicates that a wait state is not to be loaded.Default: Do not load a wait state.
- PARMLIB
- Specifies a data set
that will be included in the logical parmlib concatenation. The parmlib
concatenation consists of up to 16 PARMLIB data sets and SYS1.PARMLIB.
When there is more than one PARMLIB statement, the statements are
concatenated and SYS1.PARMLIB, as cataloged in the Master Catalog,
is added at the end of the concatenation, unless it was specified
in a parmlib. See Restrictions
for restrictions on cataloging parmlib data sets when a system symbol
is used. The parmlib concatenation is established during IPL
and is used by Master Scheduler Initialization. Programs can access
members in the logical parmlib concatenation using the IEFPRMLB macro
(see z/OS MVS Programming: Assembler Services Reference IAR-XCT).
Each additional PARMLIB statement adds another data set to the logical
parmlib concatenation.
Column Contents 1-7 PARMLIB 10-53 A required valid data set name. There is no default value. 55-60 A optional valid volume name. If a volume name is specified, IPL processing attempts to locate the specified data set on the specified volume.
If '******' or '&SYSR1' is specified, IPL processing attempts to locate the specified data set on the system residence volume.
If '*MCAT*' is specified, IPL processing attempts to locate the specified data set on the master catalog volume.
If nothing is specified, IPL processing attempts to locate the specified data set first in the master catalog and, if it is not located there, on the system residence volume.
Note: &SYSR1 is the only system symbol that can be specified in the logical parmlib concatenation.Default: If you do not specify at least 1 PARMLIB statement, the parmlib concatenation will consist of only SYS1.PARMLIB and Master Scheduler processing will use the IEFPARM DD statement, if there is one in the Master JCL. If there are no parmlib statements in the parmlib concatenation and there is no IEFPARM DD statement, Master Scheduler processing will use SYS1.PARMLIB.
Example 1: The following example shows the definition of a parmlib concatenation consisting of MYDSN1.PARMLIB, MYDSN2.PARMLIB, MYDSN3.PARMLIB. SYS1.PARMLIB, as cataloged in the master catalog, will automatically be concatenated as the last data set in the parmlib concatenation.----+----1----+----2----+----3----+----4----+----5----+----6----+----7-- PARMLIB MYDSN1.PARMLIB PARMLIB MYDSN2.PARMLIB VOL123 PARMLIB MYDSN3.PARMLIB VOL456Example 2: The following example shows the definition of a parmlib concatenation consisting of MYDSN1.PARMLIB, MYDSN2.PARMLIB, SYS1.PARMLIB on volume VOL234, MYDSN3.PARMLIB and, additionally, SYS1.PARMLIB, as cataloged in the master catalog, which will be concatenated as the last data set in the parmlib concatenation.----+----1----+----2----+----3----+----4----+----5----+----6----+----7-- PARMLIB MYDSN1.PARMLIB PARMLIB MYDSN2.PARMLIB VOL123 PARMLIB SYS1.PARMLIB VOL234 PARMLIB MYDSN3.PARMLIB VOL456Example 3: The following example shows the definition of a parmlib concatenation consisting of MYDSN1.PARMLIB, MYDSN2.PARMLIB, SYS1.PARMLIB as cataloged in the master catalog and MYDSN3.PARMLIB. SYS1.PARMLIB is not concatenated as the last data set in this case since it was already specified on a PARMLIB statement without a volume serial number and is, thus, the SYS1.PARMLIB cataloged in the master catalog.----+----1----+----2----+----3----+----4----+----5----+----6----+----7-- PARMLIB MYDSN1.PARMLIB PARMLIB MYDSN2.PARMLIB VOL123 PARMLIB SYS1.PARMLIB PARMLIB MYDSN3.PARMLIB VOL456In all of the above examples, if none of the data sets specified on the PARMLIB statements could be located, the parmlib concatenation would consist of only SYS1.PARMLIB.
- PROCVIEW
- Indicates the processor view for
the duration of the IPL.
Column Contents 1-8 PROCVIEW 10-21 {CORE | CPU | CORE,CPU_OK} - CORE
- Specifies z/OS should configure
a processor view of core, where a core can have 1-n threads. A thread
is comparable to the definition of a CPU in a pre-multithreading environment.
The number of useable threads per core is limited by what is supported
by the underlying hardware, the current z/OS release,
and the specification of MT_XXXX_MODE keywords. See the description
of these keywords in Statements/parameters for IEAOPTxx. If the underlying hardware does
not support MT, a core is limited to one thread. This parameter:
- Results in LOADxx DYNCPADD specifying the number of cores that can be dynamically added. For more information, see the DYNCPADD parameter described previously in this section.
- Requires DISPLAY M=CORE to display the core state. For more information, see the description of the DISPLAY M=CORE command in z/OS MVS System Commands.
- Requires the CONFIG CORE command to configure an entire core. For more information, see the description of the CONFIG CORE command in z/OS MVS System Commands.
- Limits the use of the MODE command. For more information, see the description of the MODE command in z/OS MVS System Commands.
For purposes of migration and coexistence, you can specify PROCVIEW CORE on systems that do not specifically support multithreading. For more information on the MT Facility, see z/Architecture Principles of Operations.
- CPU
- Specifies z/OS should configure a traditional processor view of CPU and not exploit the MT Facility.
- CORE,CPU_OK
- Specifies z/OS should manage a processor as a core; see the previous description of the CORE option. However with CORE,CPU_OK the CPU parameter is accepted as an alias for applicable commands.
Note: When PROCVIEW CORE or PROCVIEW CORE,CPU_OK is requested and the underlying hardware supports MT, partitions are forced to run with IEAOPTxx HIPERDISPATCH=YES and are unable to switch into HIPERDISPATCH=NO.Default: CPU
- SYSCAT
- Identifies the master catalog. The operator can override the
value specified on this parameter, using the LOAD parameter on the
system console with an appropriate initialization message suppression
indicator (IMSI). For more information, see the topic on loading the
system software in z/OS MVS System Commands.
Column Contents 1-6 SYSCAT 10-15 The volume serial of the device that contains the master catalog.. 16 The character “1”, unless SYS% to SYS1 conversion is active, in which case this will be a “2”. 17 Alias name level of qualification. Value Range: 1 - 4
Default: 1
18-19 CAS service task lower limit. Value Range: X'18' - X'B4'
Default: X'3C'
If you want to specify the CAS service task lower limit, specify the value with EBCDIC characters, for instance, hexadecimal B4 is specified as C'B4' or X'C2F4'.
20-63 The 44-byte data set name of the master catalog. 64-71 The 1 to 8 character high-level qualifier of the tape volume catalog. Default: SYS1
72 Specify Y to enable AUTOADD when the catalog address space (CAS) makes the first connection to the coupling facility. The AUTOADD function enables coupling facility support of enhanced catalog sharing (ECS) for eligible catalogs. Default: If you do not specify a SYSCAT statement, the system prompts the operator to specify the SYSCATxx member of SYS1.NUCLEUS.
- SYSPARM
- The SYSPARM statement identifies one or more IEASYSxx members
of the parmlib concatenation that the system is to use (in addition
to IEASYS00). To display the contents of IEASYSxx at the operator
console when the system processes each member, specify ,L anywhere
after the first suffix and enclose the values in parentheses. For
example, specify (01,L) on SYSPARM to tell the system to process IEASYS01
and display the contents of that member at the operator console. The
system ignores the SYSPARM statement if the operator specifies on
the LOAD parameter that the system should prompt for system information.
The operator can accomplish this by specifying an A, P, S, or T IMSI
character on the LOAD parameter on the system console. For details
about IMSI characters, see the topic on loading the system software
in z/OS MVS System Commands.
Note: The suffixes of IEASYSxx members can also be specified:
- On the SYSPARM parameter in the IEASYMxx parmlib member.
- By the operator, in response to message IEA101A SPECIFY SYSTEM PARAMETERS.
During system initialization, NIP first processes the IEASYS00 parmlib member to establish parameters. Then it determines, from the suffixes that are specified on the SYSPARM statement in LOADxx, the SYSPARM parameter in IEASYMxx, or by the operator, which IEASYSxx members are to be used. See Step 2. Determine where to specify system parameters for a description of how the system determines which IEASYSxx members are to be used.
To specify one IEASYSxx parmlib member, code SYSPARM as follows:Column Contents 1-7 SYSPARM 10-11 The volume serial of the device that contains the master catalog. The following example shows a SYSPARM statement that tells the system to use the IEASYS01 parmlib member:* *---+----1----+----2----+----3----+----4----+----5----+----6----+----7-- SYSPARM 01 *To specify one IEASYSxx parmlib member and display the contents of IEASYSxx at the operator console, code SYSPARM as follows:Column Contents 1-7 SYSPARM 10 A left parenthesis. 11-12 A 2-character suffix appended to “IEASYS” to select the member. 13-14 The following characters: ,L 15 A right parenthesis. The following example shows an SYSPARM statement that tells the system to use the IEASYS01 parmlib member and display the contents of IEASYSxx at the operator console.* *---+----1----+----2----+----3----+----4----+----5----+----6----+----7-- SYSPARM (01,L) *To specify more than one IEASYSxx parmlib member, code SYSPARM as follows:Column Contents 1-7 SYSPARM 10 A left parenthesis. 11-71 A list of 2-character suffixes appended to IEASYS to select members of SYS1.PARMLIB. To display the contents of IEASYSxx at the operator console when the system processes each member, specify ,L anywhere after the first suffix and enclose the values in parentheses, as shown in the example below. Default: If you do not specify a SYSPARM statement, the system prompts the operator to specify the IEASYSxx members of SYS1.PARMLIB.
The following example tells the system to use IEASYSxx members IEASYS01 and IEASYS02 and display their contents:* *---+----1----+----2----+----3----+----4----+----5----+----6----+----7-- SYSPARM (01,02,L) * - SYSPLEX
- The SYSPLEX statement specifies the name of the sysplex in which
the system participates. It is also the substitution text for the &SYSPLEX system symbol. Specify
a sysplex name that is different from the names of all the systems
that participate in the sysplex. Note: The sysplex name must match the name that is specified in both of the following places:
- The SYSPLEX parameter of the XCF couple data set format utility. See z/OS MVS Setting Up a Sysplex for information about the data set format utility.
- The SYSPLEX parameter in the COUPLExx parmlib member. LOADxx defines the substitution text for &SYSPLEX early in system initialization so other parmlib members can use it. Therefore, if you plan to use the &SYSPLEX system symbol in parmlib, specify the sysplex name in LOADxx. To ensure that the name in COUPLExx matches the one in LOADxx, specify the &SYSPLEX system symbol on the SYSPLEX parameter in COUPLExx. (See COUPLExx (cross-system coupling facility (XCF) parameters)for more information.)
Value range:Column Contents 1-7 SYSPLEX 10-17 The sysplex name. It can consist of 1 to 8 characters, left-justified in the column. Valid characters are alphanumeric (A-Z and 0-9) and national (@,#,$). Default: If you do not specify a SYSPLEX statement, the system uses the value LOCAL until it processes the COUPLExx parmlib member; then it uses the name that is specified in COUPLExx. In this case, the system substitutes LOCAL for the &SYSPLEX system symbol in all parmlib members that are processed before COUPLExx.The following example specifies that OURWORLD is the sysplex name.* *---+----1----+----2----+----3----+----4----+----5----+----6----+----7-- SYSPLEX OURWORLD * - VMUSERID
- Specifies the user ID of a z/VM system under which a z/OS image is running as a guest. This optional
filter parameter identifies a segment of LOADxx that may contain LOADxx
statements that will be used if the specified HWNAME matches the name
of the processor, the specified LPARNAME matches the actual LPAR logical
partition in which z/OS is
executing, and the specified VMUSERID matches the actual user ID of
the z/VM guest machine in which z/OS is executing.
Column Contents 1-8 VMUSERID 10-17 A required user ID name as defined to z/VM. A blank indicates an image not running under VM. The default of matching the system being IPLed is set indirectly by specifying the HWNAME or LPARNAME parameter.