Working with Multi-Version Measurement (MVM) reports

Monthly Summary Reports generated when Multi-version Measurement Pricing (MVM) is in effect differ significantly from those generated without MVM in effect.

This topic describes the differences and provides general information about how to drill down in the report to determine the factors that impacted MSU utilizations and affected your monthly costs.

MVM 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 "product 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, treated as a single MLC product.

The following figure shows a sample Monthly Summary Report that was generated from a cost model that used Multi-Version Measurement Pricing.

Figure: Sample Monthly Summary Report with Multi-Version Measurement Pricing

MSR_Mobile_Workload_product_level_new.PNG

This report groups 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) only when there are multiple versions of the MLC product running on any CPC. The MLC product family row provides only the R4HA First Peak Cost data and the Percent of Total Cost data. Cost Analyzer determines these values by combining the cost of running all versions of the MLC product on each CPC. The rest of the the data columns are left blank. 

Under the MLC product family name is a list of each CPC running versions of the MLC Product. For each CPC, a corresponding R4HA MSU utilization chart shows the combined peak and the resulting cost data. The peak R4HA MSU utilization value for each CPC represents the combined utilizations for all versions of the MLC product. When MVM is in effect, this combined R4HA peak determines the cost of the MSU utilizations for each version of the MLC product.

The MLC product family section  also has entries for each individual version of the MLC product. Each MLC product version lists the CPCs where the product was running and shows a chart that identifies the peak value of the R4HA MSU Utilization. However, because the monthly cost is based on the peak value of all versions combined, the monthly summary report cannot provide data for actual costs, the percentage of total costs, or the average and incremental costs per MSU for any individual MLC product version. These values will always be zero.

Note

If a CPC is running only one version of the MLC product, the chart and R4HA peak are identical for both the MLC product family entry and for the specific MLC product version entry.

In the previous figure, CPC PSYSBBBB is running only version 5 of CICS TS for z/OS. Thus, the chart and R4HA peaks are the same, but the cost data is provided only in the CICS All entry. Similarly, CPC PSYSAAAA and CPC PSYSCCCC are running both version 5 and version 4 of CICS TS for z/OS. Thus, the charts and R4HA peaks are different for each version, and the CICS All entry provides a chart that represents the combined activity for running both versions.

Even though the individual charts and peaks are provided for each version of the MLC product, they do not affect the actual cost (unless the MLC product version is the only version running on the CPC). For MLC product versions in the report, the charts and R4HA peaks give you additional information about the utilizations at the product-version level. They can give you important information especially when there are multiple versions of the MLC product running on the CPC.

By clicking the black triangle ( GUID-6D4329E7-1076-4788-85D6-11629C3C407A-low.png), you can expand any entry of the report to show this information:

  • A breakdown of the monthly cost data for each CPC
  • The contribution of each CPC to the combined R4HA peak (that is, the total R4HA MSU utilization of each CPC in the interval of the combined peak).

By clicking any column header of the report, you can sort the report based on that column's data. For instance, click the % of Total Cost column to configure the report to show the data based on the highest to lowest percentage of the total cost. To restore the family sections, click the MLC Product column header.

As with all 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

MLC Product

Any MLC Product family name or MLC Product version name that has Priced Features

Note

If the MLC product name appears in blue text, this indicates a link is available.

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:

  • Work with the charting area to compare R4HA MSU Utilizations of one or more MLC products

  • Access hyperlinks to the CPC R4HA details, which shows a breakdown of the utilizations by LPAR

    See the information about CPC level and MLC level in Drill-down-levels.

  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 versionYou 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 runningYou 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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*