Chapter 2. System structure and design 61
Draft Document for Review April 7, 2004 6:15 pm 6947ch02.fm
Table 2-4 LPAR mode and PU usage

Dynamic Add/Delete of a logical partition name

The ability to add meaningful logical partition names to the configuration without a Power-On
Reset is being introduced. Prior to this support, extra logical partitions were defined by adding
reserved names in the Input/Output Configuration Data Set (IOCDS), but one may not have
been able to predict what might be meaningful names in advance.
Dynamic add/delete of a logical partition name allows reserved logical partition 'slots' to be
created in an IOCDS in the form of extra logical channel subsystem (CSS), Multiple Image
Facility (MIF) image ID pairs. A reserved partition is defined with the partition name
placeholder ‘ * ’, and cannot be assigned to access or candidate list of channel paths or
devices. These extra logical channel subsystem MIF image ID pairs (CSSID/MIFID) can be
later assigned an logical partition name for use (or later removed) via dynamic I/O commands
using the Hardware Configuration Definition (HCD). The IOCDS still must have the extra I/O
slots defined in advance since many structures are built based upon these major I/O control
blocks in the Hardware System Area (HSA). This support is exclusive to the z990 and z890
and is applicable to z/OS V1.6, which is planned to be available in September 2004.
When a logical partition is renamed, its name can be changed from ’NAME1’ to ‘ * ’ and then
changed again from ‘ * ’ to ‘NAME2’, the logical partition number and MIFID are retained
across the logical partition name change. However, the master keys in PCIXCC that were
associated with the old logical partition ‘NAME1’ are retained. There is no explicit action taken
against a cryptographic component for this.
2.2.7 Model configurations
The z990 server model nomenclature is based on the number of PUs available for customer
use in each configuration. Four models of the z990 server are available:
򐂰IBM 2084 model A08 - 8 PUs are available for characterization as CPs, IFLs, ICFs, zAAPs
(up to 4), or additional SAPs
LPAR mode PU type Operating systems PUs usage
ESA/390 CPs z/Architecture operating systems
ESA/390 operating systems
Linux
CPs DED or CPs SHR
CPs and
zAAPs z/OS (1.6 and later) CPs DED and zAAPs DED, or
CPs SHR and zAAPs SHR
ESA/390 TPF CPs TPF CPs DED or CPs SHR
Coupling
Facilit y ICFs
and/or
CPs
CFCC ICFs DED or ICFs SHR, or
CPs DED or CPs SHR, or
ICFs DED and ICFs SHR, or
ICFs DED and CPs SHR
Linux Only IFLs or
CPs Linux
z/VM IFLs DED or IFLs SHR, or
CPs DED or CPs SHR
Attention: Cryptographic cards are not tied to partition numbers or MIFIDs. They are set
up with AP numbers and domain indices. These are assigned to a partition profile of a
given name. The customer assigns these "lanes" to the partitions now and continues to
have responsibility to clear them out if he changes who is using them.