Ordering - IBM z13s Technical Manual

8.5.2 Ordering

Concurrently installing temporary capacity by ordering On/Off CoD is possible in the following
quantities:
CP features equal to the MSU capacity of installed CPs
IFL features up to the number of installed IFLs
ICF features up to the number of installed ICFs
zIIP features up to the number of installed zIIPs
SAPs up to two for both models
On/Off CoD can provide CP temporary capacity by increasing the number of CPs, by
changing the capacity setting of the CPs, or both. The capacity setting for all CPs must be the
same. If the On/Off CoD is adding CP resources that have a capacity setting that differs from
the installed CPs, the base capacity settings are changed to match.
On/Off CoD has the following limits associated with its use:
The number of CPs cannot be reduced.
The target configuration capacity is limited in these ways:
– Twice the currently installed capacity, expressed in MSUs for CPs.
– Twice the number of installed IFLs, ICFs, and zIIPs. The number of additional SAPs
that can be activated is two.
See Appendix D, "Shared Memory Communications" on page 475 for the valid On/Off CoD
configurations for CPs.
On/Off CoD can be ordered as prepaid or postpaid:
A prepaid On/Off CoD offering record contains the resource descriptions, MSUs, number
of speciality engines, and tokens that describe the total capacity that can be consumed.
For CP capacity, the token contains MSU-days. For speciality engines, the token contains
speciality engine-days.
When resources on a prepaid offering are activated, they must have enough capacity
tokens to support the activation for an entire billing window, which is 24 hours. The
resources remain active until you deactivate them or until one resource has used all of its
capacity tokens. When that happens, all activated resources from the record are
deactivated.
A postpaid On/Off CoD offering record contains resource descriptions, MSUs, and
speciality engines, and can contain capacity tokens for MSU-days and speciality
engine-days.
When resources in a postpaid offering record without capacity tokens are activated, those
resources remain active until they are deactivated, or until the offering record expires,
which is usually 180 days after its installation.
When resources in a postpaid offering record with capacity tokens are activated, those
resources must have enough capacity tokens to support the activation for an entire billing
window (24 hours). The resources remain active until they are deactivated or until one of
the resource tokens is consumed, or until the record expires, usually 180 days after its
installation. If one capacity token type is consumed, resources from the entire record are
deactivated.
334
IBM z13s Technical Guide