IBM z13s, Техническое руководство

Страница: 361 / 588

Chapter 8. System upgrades
333
8.5.1 Overview
The capacity for CPs is expressed in MSUs. The capacity for speciality engines is expressed
in the number of speciality engines.
Capacity tokens
are used to limit the resource
consumption for all types of processor capacity.
Capacity tokens are introduced to provide better control over resource consumption when
On/Off CoD offerings are activated. Tokens are represented in the following manner:
򐂰 For CP capacity, each token represents the amount of CP capacity that will result in one
MSU of software cost for one day (an
MSU-day token
).
򐂰
For speciality engines, each token is equivalent to one speciality engine capacity for one
day (an
engine-day token
).
Tokens are by capacity type, MSUs for CP capacity, and number of engines for speciality
engines. Each speciality engine type has its own tokens, and each On/Off CoD record has
separate token pools for each capacity type. During the ordering sessions on Resource Link,
you decide how many tokens of each type must be created in an offering record. Each engine
type must have tokens for that engine type to be activated. Capacity that has no tokens
cannot be activated.
When the resources from an On/Off CoD offering record that contains capacity tokens are
activated, a
billing window
is started. A billing window is always 24 hours in length. Billing
takes place at the end of each billing window. The resources that are billed are the highest
resource usage inside each billing window for each capacity type.
An
activation period
is one or more complete billing windows. It represents the time from the
first activation of resources in a record until the end of the billing window in which the last
resource in a record is deactivated.
At the end of each billing window, the tokens are decremented by the highest usage of each
resource during the billing window. If any resource in a record does not have enough tokens
to cover usage for the next billing window, the entire record is deactivated.
On/Off CoD requires that the Online CoD Buying feature (FC 9900) be installed on the server
that is to be upgraded.
The On/Off CoD to Permanent Upgrade Option is a new offering, which is an offshoot of
On/Off CoD and takes advantage of aspects of the architecture. The customer is given a
window of opportunity to assess the capacity additions to the customer’s permanent
configurations using On/Off CoD. If a purchase is made, the hardware On/Off CoD charges
during this window, three days or less, are waived. If no purchase is made, the customer is
charged for the temporary use.
The resources that are eligible for temporary use are CPs, ICFs, zIIPs, IFLs, and SAPs. The
temporary addition of memory is not supported. Unassigned PUs that are on the installed
CPC drawers can be temporarily and concurrently activated as CPs, ICFs, zIIPs, IFLs, and
SAPs through LICCC, up to twice the currently installed CP capacity and up to twice the
number of ICFs, zIIPs, or IFLs.
An On/Off CoD upgrade cannot change the model from an N10 to an N20. The addition of a
new CPC drawer is not supported. However, the activation of an On/Off CoD upgrade can
increase the MCI.