Capacity tokens are introduced to provide better control over resource consumption when On/Off CoD offerings are activated. Tokens represent the following resource consumptions: 

GLYPH<SM590000> For CP capacity, each token represents the amount of CP capacity that results in one MSU of software cost for one day (an MSU-day token ). 

GLYPH<SM590000> For speciality engines, each token is equivalent to one speciality engine capacity for one day ( an engine-day token ). 

Each speciality engine type features its own tokens, and each On/Off CoD record includes separate token pools for each capacity type. During the ordering sessions on Resource Link, select how many tokens of each type to create for an offering record. Each engine type must include tokens for that engine type to be activated. Capacity that has no tokens cannot be activated. 

When 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. Billing occurs 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. The activation period is 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. 

Note:  On/Off CoD requires that the Online CoD Buying feature (FC 9900) is installed on the system that you want to upgrade. 

The On/Off CoD to Permanent Upgrade Option is a new offering. It is an offshoot of On/Off CoD that takes advantage of aspects of the architecture. You are given a window of opportunity to assess capacity additions to your permanent configurations by 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, you are charged for the temporary use. 

The resources eligible for temporary use are CPs, ICFs, zIIPs, IFLs, and SAPs. The temporary addition of memory and I/O ports or adapters is not supported. 

Unassigned PUs that are on the installed processor drawers can be temporarily and concurrently activated as CPs, ICFs, zIIPs, IFLs, and SAPs through LICCC. You can assign PUs up to twice the currently installed CP capacity, and up to twice the number of ICFs, zIIPs, or IFLs. Therefore, an On/Off CoD upgrade cannot change the system model. The addition of new processor drawers is not supported. However, the activation of an On/Off CoD upgrade can increase the model capacity identifier (4 xx , 5 yy , 6 yy , or 7 nn ). 

## 8.5.2 Capacity Provisioning Manager 

The installation of the capacity provision function on z/OS requires the following prerequisites: 

GLYPH<SM590000> Setting up and customizing z/OS RMF, including the Distributed Data Server (DDS). 

GLYPH<SM590000> Setting up the z/OS CIM Server (included in z/OS base). 

GLYPH<SM590000> Performing capacity provisioning customization. For more information, see z/OS MVS Capacity Provisioning User’s Guide , SA33-8299. 

