IBM z13s Technical Manual page 37

capacity that is consumed by an individual LPAR or by a group of LPARs. This limit is still valid
when a PU defined as a CP or an IFL is shared across a set of LPARs. This feature is
designed to provide and enforce a physical capacity limit as an absolute (versus a relative)
limit. Physical capacity limit enforcement is not affected by changes to the logical or physical
configuration of the system. This physical capacity limit can be specified to a fine level of
granularity, to hundredths of units of a processor.
z13s servers provide improvements to the PR/SM HiperDispatch function.
provides work alignment to logical processors, and alignment of logical processors to physical
processors. This alignment optimizes cache utilization, minimizes inter-CPC drawer
communication, and optimizes z/OS work dispatching, with the result of increasing
throughput. For more information, see "HiperDispatch" on page 87
z13s servers support the definition of up to 32 IBM HiperSockets.
memory to memory communication across LPARs without the need for any I/O adapters, and
have virtual LAN (VLAN) capability. HiperSockets have been extended to bridge to the
intraensemble data network (IEDN).
Increased flexibility with z/VM mode logical partition
z13s servers provide for the definition of a z/VM mode LPAR containing a mix of processor
types. These types include CPs and specialty processors, such as IFLs, zIIPs, and ICFs.
z/VM V6R2 and later support this capability, which increases flexibility and simplifies system
management. In a single LPAR, z/VM can perform the following tasks:
Manage guests that use Linux on z Systems on IFLs or CPs, and manage IBM z/VSE,
z/TPF, and z/OS guests on CPs.
Run designated z/OS workloads, such as parts of IBM DB2 Distributed Relational
Database Architecture™ (DRDA®) processing and XML, on zIIPs.
Coupling Facility mode logical partition
Parallel Sysplex is the clustering technology used with z13s servers. To use this technology, a
special LIC is used. This code is called CFCC. To activate the CFCC, a special logical
partition must be defined. Only PUs characterized as CPs or Internal Coupling Facilities
(ICFs) can be used for Coupling Facility (CF) partitions. For a production CF workload, use
dedicated ICFs.
IBM z Appliance Container Infrastructure
z Appliance Container Infrastructure (zACI) s a new partition type that, along with an
appliance installer, enables the secure deployment of software appliances.Typically,
appliances can be implemented as firmware or software, depending on the environment
where the appliance runs. To support the execution of software applications, base
infrastructure is needed. This partition with its infrastructure is the z Appliance Container
Infrastructure. zACI is designed to shorten the deployment and implementation of building
and deploying appliances. zACI will be delivered as part of the base code on z13s and z13
(Driver 27) servers.
zACI provides a standardized framework for deploying products as software or firmware. An
appliance is an integration of operating system, middleware, and software components that
work autonomously and provide core services and infrastructure that focus on consumability
and security.
zACI reduces the work that is needed to create and maintain a product, and enforces
common functions that appliances need. The zACI framework provides a consistent set of
utilities to implement these common functions such as first failure data capture (FFDC),
HiperDispatch
HiperSockets
Chapter 1. Introducing IBM z13s servers
provide for
9