IBM z13s Technical Manual page 150

Table of Contents

Advertisement

Table 3-5 shows all LPAR modes, required characterized PUs, operating systems, and the PU
characterizations that can be configured to an LPAR image. The available combinations of
dedicated (DED) and shared (SHR) processors are also shown. For all combinations, an
LPAR also can have reserved processors that are defined, allowing nondisruptive LPAR
upgrades.
Table 3-5 LPAR mode and PU usage
LPAR mode
ESA/390
ESA/390 TPF
Coupling
facility
Linux only
z/VM
a
zACI
a. z Appliance Container Infrastructure
b. Encapsulated as a firmware appliance.
c. Planned
Dynamically adding or deleting a logical partition name
Dynamically adding or deleting an LPAR name is the ability to add or delete LPARs and their
associated I/O resources to or from the configuration without a POR.
The extra channel subsystem and multiple image facility (MIF) image ID pairs (CSSID/MIFID)
can be later assigned to an LPAR for use (or later removed). This process can be done
through dynamic I/O commands by using HCD. At the same time, required channels must be
defined for the new LPAR.
Partition profile: Cryptographic coprocessors are not tied to partition numbers or MIF IDs.
They are set up with Adjunct Processor (AP) numbers and domain indexes. These are
assigned to a partition profile of a given name. The client assigns these AP numbers and
domains to the partitions and continues to have the responsibility to clear them out when
their profiles change.
Adding logical processors to a logical partition
Logical processors can be concurrently added to an LPAR by defining them as reserved in
the image profile and later configuring them online to the operating system by using the
appropriate console commands. Logical processors can also be concurrently added to a
logical partition dynamically by using the Support Element "Logical Processor Add" function
under the "CPC Operational Customization" task. This SE function allows the initial and
reserved processor values to be dynamically changed. The operating system must support
122
IBM z13s Technical Guide
PU type
Operating systems
CPs
z/Architecture operating systems
ESA/390 operating systems
Linux on z Systems
and
CPs
z/OS
zIIPs
z/VM (V6R2 and later for guest
exploitation)
CPs
z/TPF
or
ICFs
CFCC
CPs
or
IFLs
CPs
Linux on z Systems
z/VM
CPs, IFLs,
z/VM (V6R2 and later)
zIIPs, or
ICFs
IFLs, or CPs
IBM zAware
IBM z/VSE Network Appliance
PUs usage
CPs DED or CPs SHR
CPs DED
or
CPs SHR
CPs DED or CPs SHR
ICFs DED
CPs DED
IFLs DED
CPs DED
All PUs must be SHR or DED
b
IFLs DED
c
CPs DED
and
or
(
) zIIPs DED
and
(or) zIIPs SHR
or
or
ICFs SHR,
or
CPs SHR
or
or
IFLs SHR,
or
CPs SHR
or
or
IFLs SHR,
or
CPs SHR

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents