content_image/974800.jpg
GLYPH<SM590000> SSC (Secure Service Container) mode LPAR can run on: 

– Dedicated or shared CPs 

– Dedicated or shared IFLs 

All LPAR modes, required characterized PUs, operating systems, and the PU characterizations that can be configured to an LPAR image are listed in Table 3-5. The available combinations of dedicated (DED) and shared (SHR) processors are also included. For all combinations, an LPAR also can include reserved processors that are defined, which allows for nondisruptive LPAR upgrades. 

<img src='content_image/974800.jpg'>

a. ESA/390 operating systems cannot be IPL’ed on z14 ZR1. Limited support for z/VM guests. 

b. Secure Service Container 

## 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 assigned later to an LPAR for use (or later removed). This process can be done through dynamic I/O commands by using the 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 numbers are assigned to a partition profile of a specific 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. 

