LPARS AND SYSTEMS Policy Item
If you have created a Processor policy object with LPAR mode, the policy item LPARS AND SYSTEMS is available, and has the LPAR Definitions panel shown in Figure 1 associated with it.
COMMANDS ACTIONS HELP
------------------------------------------------------------------------------
AOFGXC4P LPAR Definitions Row 1 to 13 of 20
Command ===> SCROLL===> PAGE
Entry Type : Processor PolicyDB Name : USER_PDB
Entry Name : PROC1 Enterprise Name : USER_ENTERPRISE
Action LPAR Name Target Mode Target System Name
LPAR1 SSC SYSZAPP1
LPAR2 LINUX SYSKVM1
LPAR3 LINUX SYSLNX1
LPAR4 ESA SYSMVS1
LPAR5 ESA
You can specify the following:
- Action
- Action allows you to remove LPAR
definitions and to invoke the system selection panel:
- DELETE (D) deletes the current LPAR definition. Confirmation on a separate panel is not required.
- SYSTEM (S) displays a selection list of all defined systems allowing a system to link to the current LPAR.
- LPAR Name
- Specifies the name of the logical partition. Duplicate LPAR names without Target System Name are wiped out when the panel is left. However, it is possible to link different systems to one LPAR, so duplicate LPAR names are accepted when they have links to different systems. Linking one system to multiple LPARs is not accepted.
- Target Mode
- Specifies the mode of the system that is
supposed to run in this LPAR.
Valid LPAR Target Modes are 370, ESA, CF, LINUX, and SSC.
Valid VM GUEST Target Modes are 370, ESA, and LINUX.
The Target Mode LINUX is used for hardware that supports LPARs for Linux® only, where a reduced instruction set is provided and therefore cannot run MVS or VM. For a Linux system, specify LINUX if the processor hardware is configured in 'LINUX Only' mode, otherwise specify ESA.
The Target Mode SSC is used for LPARs that run as a Secure Service Container (SSC).
For compatibility reasons, the specification of former zACI (z Appliance Container Infrastructure) mode is still allowed.
- Target System Name
- You can specify a system entry name, which establishes a "link" of this system to the partition. Any name is allowed here, it is not required that the system entry has already been defined. During build, such an undefined system is treated as not specified. If the system is already defined as SYS entry, it is checked that it is a valid selection according to the rules described in the following section for entry type SYS. Otherwise, an error message is displayed.