## Maintenance 

The maintenance price is adjusted as a result of an On/Off CoD activation. 

## Software 

Software Parallel Sysplex license charge (PSLC) clients are billed at the MSU level that is represented by the combined permanent and temporary capacity. All PSLC products are billed at the peak MSUs that are enabled during the month, regardless of usage. Clients with WLC licenses are billed by product at the highest four-hour rolling average for the month. In this instance, temporary capacity does not increase the software bill until that capacity is allocated to LPARs and used. 

Results from the STSI instruction reflect the current permanent and temporary CPs. For more information, see “Store System Information instruction” on page 376. 

## 8.6 z/OS Capacity Provisioning 

This section describes how z/OS Capacity Provisioning can help you manage the addition of capacity to a server to handle workload peaks. 

z/OS Capacity Provisioning is delivered as part of the z/OS MVS™ Base Control Program (BCP). 

Capacity Provisioning includes the following components: 

GLYPH<SM590000> Capacity Provisioning Manager (Provisioning Manager) 

GLYPH<SM590000> Capacity Provisioning Management Console, available in the IBM z/OS Management Facility 

GLYPH<SM590000> Sample data sets and files 

The Provisioning Manager monitors the workload on a set of z/OS systems and organizes the provisioning of extra capacity to these systems when required. You define the systems to be observed in a domain configuration file. 

The details of extra capacity and the rules for its provisioning are stored in a policy file. These two files are created and maintained through the Capacity Provisioning Management Console (CPMC).The operational flow of Capacity Provisioning is shown in Figure 8-13 on page 364. 

