*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
NUCLEUS 1
NUCLST 00
*This segment applies to any machine in any logical partition (or
*not in LPAR mode).
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
SYSPARM 01
PARMLIB ALLSYS.PARMLIB
*This segment applies to an IPL on VM user ID V1 on any LPAR (or not
*in LPAR mode), and on any hardware.
*Note that at this point neither HWNAME
*nor LPARNAME have been specified in the LOADxx member, so they
*will automatically match those of the system being IPLed.
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
VMUSERID V1
IEASYM V1
SYSPARM V1
*This segment applies to any IPL on VM user ID V2 on any LPAR (or not
*in LPAR mode), and on any hardware.
*Note that at this point neither HWNAME
*nor LPARNAME have been specified in the LOADxx member, so they
*will automatically match those of the system being IPLed.
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
VMUSERID V2
IEASYM V2
SYSPARM V2
PARMLIB V2.PARMLIB
*This segment applies to an IPL in logical partition L1 on any hardware
*and not under any VM user ID (or not under VM).
*Note that at this point HWNAME has not been specified in the LOADxx member,
*so it automatically matches the system being IPLed.
*Also note that specification of LPARNAME
*causes the VMUSERID filter to be reset to match the system being IPLed.
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
LPARNAME L1
IEASYM L1
SYSPARM L1
*This segment applies to an IPL on machine H1 in any logical partition
*(or not in LPAR mode) and under any VM user ID (or not under VM).
*Note that specification of HWNAME
*causes the LPARNAME and VMUSERID filters to be reset to match the
*system being IPLed.
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
LPARNAME L2
IEASYM BB
PARMLIB L2.PARMLIB
*This segment applies to an IPL on machine H1 in logical partition L2
*not running under VM.
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
VMUSERID
IEASYM CC
PARMLIB NOT.VM.PARMLIB
*This segment applies to an IPL on machine H1 running in non-LPAR mode
*under any VM user ID (or not under VM). The specification of
*LPARNAME causes the VMUSERID filter to be reset to match the system
*being IPLed.
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
LPARNAME
IEASYM DD
PARMLIB NOT.LPAR.PARMLIB
*This segment applies to an IPL on machine H2 in any logical partition
*(or not in LPAR mode), under any VM user ID (or not under VM).
*The specification of HWNAME causes the LPARNAME
*and VMUSERID filters to be reset.
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
HWNAME H2
SYSPARM H2
PARMLIB H2.PARMLIB
*This is only *one* LOADxx.
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
HWNAME H1
SYSPARM H1
PARMLIB H1.PARMLIB
*This segment applies to an IPL on machine H1 in logical partition L2
*not under any VM user ID (or not under VM).
Table 1 summarizes some of the IPL results produced by the examples in Figure 1. Note that use of a second PARMLIB statement adds to the list of parmlibs. For any other statement, the previous value is replaced.
IPL | LOADxx Members |
---|---|
IPL on hardware H1 with logical partition L0 not under z/VM®. |
|
IPL on hardware H1 with logical partition L1 under VMUSERID V1. |
|
IPL on hardware H1 with logical partition L2 under VMUSERID V0. |
|
IPL on hardware H1 with logical partition L2 not under z/VM. |
|
IPL on hardware H1, not in LPAR mode, and not under VMUSERID V2. |
|
IPL on hardware H2, not in LPAR mode, and not under VMUSERID V1 or V2. |
|
IPL on hardware H2 under VMUSERID V2 in logical partition L0. |
|
IPL on unnamed hardware with logical partition L1 not under VMUSERID V1 or V2. |
|