Integrated Facility For Linux; Internal Coupling Facility - IBM z13s Technical Manual

A00: Model capacity identifier A00 is used for IFL or ICF configurations only.
For more information about capacity settings, see 2.7, "Model configurations" on page 69.

3.5.3 Integrated Facility for Linux

An Integrated Facility for Linux (IFL) is a PU that can be used to run Linux, Linux guests on
z/VM operating systems, kernel-based virtual machine (KVM) for IBM z, and IBM zAware. Up
to 20 PUs can be characterized as IFLs, depending on the configuration. IFLs can be
dedicated to a Linux, a z/VM, or an IBM zAware LPAR, or they can be shared by multiple
Linux guests, z/VM LPARs, or IBM zAware running on the same z13s server. Only z/VM,
Linux on z Systems operating systems, KVM for z, IBM zAware, and designated software
products can run on IFLs. IFLs are orderable by using FC 1924.
IFL pool
All PUs that are characterized as IFLs within a configuration are grouped into the IFL pool.
The IFL pool can be seen on the HMC workplace.
IFLs do not change the model capacity identifier of z13s servers. Software product license
charges that are based on the model capacity identifier are not affected by the addition of
IFLs.
Unassigned IFLs
An IFL that is purchased but not activated is registered as an unassigned IFL (FC 1928).
When the system is later upgraded with an additional IFL, the system recognizes that an IFL
already was purchased and is present.

3.5.4 Internal Coupling Facility

An Internal Coupling Facility (ICF) is a PU that is used to run the CFCC for Parallel Sysplex
environments. Within the capacity of the sum of all unassigned PUs in two CPC drawer
configuration, up to 20 ICFs can be characterized, depending on the model. However, the
maximum number of ICFs that can be defined on a coupling facility LPAR is limited to 16.
ICFs are orderable by using FC 1925.
ICFs exclusively run CFCC. ICFs do not change the model capacity identifier of z13s servers.
Software product license charges that are based on the model capacity identifier are not
affected by the addition of ICFs.
All ICFs within a configuration are grouped into the ICF pool. The ICF pool can be seen on the
Hardware Management Console (HMC) workplace.
The ICFs can only be used by coupling facility LPARs. ICFs are either dedicated or shared.
ICFs can be dedicated to a CF LPAR, or shared by multiple CF LPARs that run on the same
system. However, having an LPAR with dedicated and shared ICFs at the same time is not
possible.
Chapter 3. Central processor complex system design
103