Working with Country Multiplex Pricing reports
This topic describes the differences and provides general information about how to drill down in the report to determine the factors that impacted MSU utilization and your monthly costs.
Country Multiplex Pricing changes the method by which IBM determines the peak R4HA MSU utilization value that is used to calculate your monthly MLC costs. When multiple versions of an MLC product are running on the same CPC, IBM creates a family for that product and appends All to the product name (For example, z/OS All). IBM then calculates the MLC cost for that product based on the combination of all versions running on that CPC. It is treated as a single MLC product.
The following figure shows a sample MLC Monthly Summary Report that is generated from a cost model using Country Multiplex Pricing:
This report groups the product families into separate sections that are separated by lines. The top row of each section presents the MLC product family name (appended with the word All). The MLC product family entry provides the monthly cost data determined by the peak R4HA MSU utilization value. This row represents the combined utilization for all versions of this MLC product.
Under the MLC product family name is a list of each version of the MLC product that was running during the month. These entries provide the peak values of the R4HA MSU Utilization for each individual version of the MLC product. However, because the monthly cost is based on the peak value of all versions combined, the MLC Monthly Summary Report cannot provide data for actual costs, the percentage of total costs, or the average and incremental costs per MSU. These values will always be zero.
For each chart, distinct peak indicators show different types of peak values. The following table lists the peak indicator types and describes their meaning and effect on the monthly cost:
Peak name | Peak indicator | Description |
---|---|---|
Multiplex Peak Contribution (MSU) | Indicates the peak value of the combined R4HA MSU utilization activity from all CPCs IBM uses this value to determine the monthly costs for this MLC product family. | |
CPC First Peak (MSU) | Indicates the peak R4HA MSU utilization for the individual CPC This peak value is not used to determine the monthly costs for this version of the MLC product. | |
Both Peaks | Indicates that the Multiplex Peak and CPC First Peak occurred during the same interval |
By clicking the black triangle, you can expand any entry on the report to show:
- A breakdown of the monthly cost data for each CPC
- The contribution of each CPC to the Multiplex Peak (that is, the total 4HRA MSU utilization of each CPC in the interval of the Multiplex Peak).
By clicking any report column header, you can sort the report based on that column's data. For instance, click the % of Total Cost column to sort the report in ascending order based on the % of Total Cost data. To restore the family sections, click the Product column header.
As with all MLC Monthly Summary Reports, the data also serves as hyperlinks that let you drill down to details about specific CPCs and MLC products. The following table describes the columns that contain data hyperlinks:
Column | Hyperlink | Description |
---|---|---|
Product | Any MLC product family name or MLC product version name that has Priced Features | Hyperlinks to details that list the Priced Features for the MLC product and their relevant R4HA |
CPC Name | Any CPC name in the column | Hyperlinks to CPC details You can:
|
Combined MSU Reduction | Any CPC MSU Reduction value for an MLC product version | Hyperlinks to a report that details the MLC product's Combined MSU Reduction on the CPC For more information, see Working-with-combined-MSU-reduction-data. |
R4HA MSU Utilization chart | Any MLC Product family chart or MLC Product version chart | Hyperlinks to individual CPC R4HA details for the selected MLC Product family or MLC product version You can:
|
Any CPC chart
| Hyperlinks to the R4HA MSU Utilization details for each LPAR on which this MLC Product family or MLC product version is running You can:
|