Fixed PVU and VPC values for instances running in the warm standby mode
Available from 9.2.27. The licensing model of some IBM products, for example DB2, defines that product instances that run in the warm standby mode consume a fixed number of PVUs or VPCs. To report metric utilization by such product instances, assign them with the PVU Warm Standby or VPC Warm Standby metric.
Starting from application update 9.2.34, PVU Warm Standby and VPC Warm Standby metric calculation is modified. If there are multiple instances of a product on a single computer, the fixed PVU or VPC is counted only once.
Fixed values
- 100 PVUs if the product is assigned the PVU Warm Standby metric.
- 1 VPC if the product is assigned the VPC Warm Standby metric.
Calculating and reporting the utilization
- PVU subcapacity and VPC
-
Utilization of the PVU Warm Standby or VPC Warm Standby metric is reported separately from the utilization of the PVU subcapacity or VPC metric for the product. To obtain the final utilization of the license metric, add the two values that are reported on the All Metrics report or in the audit snapshot. For example, IBM DB2 Enterprise Server Edition Processor Value Unit consumes the following number of PVUs.
- 1200 PVUs under the subcapacity license.
- 300 PVUs by instances that run in the warm standby mode.

- PVU full capacity
-
If you report PVU full capacity instead of the PVU subcapacity for a product, assign all product instances, including the ones that run in the warm standby mode, to the PVU license metric. Do not assign any product instances to the PVU Warm Standby metric.
- Flex Point offerings and Cloud Paks
-
If the product is further assigned to a Flex Point offering or a Cloud Pak, manual calculation is not needed. The two values are automatically summed up while License Metric Tool calculates the overall metric utilization for the FlexPoint offering or a Cloud Pak. For example, IBM DB2 Enterprise Server Edition Processor Value Unit consumes the following number of PVUs.
- 1200 PVUs under the subcapacity license.
- 300 PVUs by instances that run in the warm standby mode.
Temporary classification is not supported
Software classification actions are not applied from the moment when they are performed. They affect the entire licensing history. For example, if a component is detected in January, and then the metric of the product to which the component is assigned is changed in May, the change affects the component from January. The change is visible after you click Recalculate on the All Metrics report or after the next import of data completes.
Due to this behavior, it is not possible to have a software instance temporarily classified as Warm Standby. If an instance is classified as Warm Standby, its license is calculated according to the Warm Standby licensing rules for the entire detection history. If it is not classified as Warm Standby, it is not counted under that rule at all.
Adding the PVU Warm Standby or VPC Warm Standby metric to a product
The software catalog contains a number of products for which the license agreement states that product instances that run in the warm standby mode consume 100 PVUs or 1 VPC per endpoint where product instance was installed. If the license agreement for your product states the same, but the option to assign the PVU Warm Standby or VPC Warm Standby metric is not available, add the metric on the Products & Metrics report. For more information, see: Assigning an additional metric to a product.
Other uses
If the license agreement for your product states that the product uses 100 PVUs or 1 VPC per instance in a scenario other than the warm standby mode, for example the hot standby mode, you can assign the product with the PVU Warm Standby or VPC Warm Standby metric.