Overview of the CPC Configuration Editor
Use the CPC Configuration Editor to configure the CPCs of your enterprise with your IBM contract so that all pricing arrangements are accounted for and included in the cost models.
The CPC Configuration Editor enables you to control the pricing method to apply to each CPC when building the cost models. For each CPC, you can specify one of the following methods:
- Sysplex Pricing
Country Multiplex Pricing
For each CPC, the CPC Configuration Editor lists the default pricing metric type applied to the cost models for all MLC products on that CPC. If applicable, the configuration also specifies the PricingPlex that aggregates the MSU utilization of the CPC into a group for pricing purposes.
The following figure shows a sample CPC Configuration Editor:
Figure: Sample CPC Configuration Editor
How the configuration determines the Pricing Metric Type
In general, the Pricing Metric Type default is determined by the CPU type you are using. However, depending upon your contractual agreement with IBM, your Pricing Metric Type may vary from these established defaults. The CPC Configuration Editor provides you with the ability to edit the value of the Pricing Metric Type to account for any variation that may exist for your enterprise.
How the configuration determines County Multiplex Pricing
Cost Analyzer cannot automatically determine whether Country Multiplex Pricing applies to your enterprise. However, you can specify to use Country Multiplex Pricing when building cost models by setting the Use Country Multiplex Pricing? toggle to Yes.
After you set the toggle to use Country Multiplex Pricing, the CPC Configuration editor changes the display to indicate CMLC (Country Multiplex Licensing Charge) as the pricing metric type for each CPC. If you use Country Multiplex Pricing, CMLC is the only supported pricing metric type.
Once you have changed the configuration to use Country Multiplex Pricing, you must rebuild the cost models for each affected month in order to generate Monthly Summary reports that contain CMP data. For more information, see Managing-Country-Multiplex-Pricing.
How the configuration determines the PricingPlex parameter
Cost Analyzer defines the PricingPlex for each CPC by determining the most active Sysplex to which the CPC is connected. However, your actual PricingPlex groupings may be different, so you can use the CPC Configuration Editor to add or change the PricingPlex parameter. If a CPC is not part of a PricingPlex, you can also edit the PricingPlex parameter so that its designation is blank, indicating that a PricingPlex does not apply to this CPC.
After you verify or change the PricingPlex parameter for each CPC, Cost Analyzer does not apply the changes to the costs that are generated in the Monthly Summary Report unless the Use Sysplex Pricing? toggle is set to Yes.
If the Use Sysplex Pricing? is set to No, the PricingPlex groupings indicated in the PricingPlex column have no affect on cost calculations.
How the CPC Configuration is updated
Each time a Model Builder Task runs and a Cost Model is built, the CPC Configuration is updated from the most recent costing data. However, Cost Analyzer only applies the updates to the parameters that are saved in the CPC Configuration Editor when certain conditions are met. Updates to the parameters saved in the CPC Configuration Editor are applied as follows:
- Cost Analyzer adds any new CPCs to the CPC configuration with a default Pricing Metric Type and PricingPlex designation that requires your verification.
- Cost Analyzer does not change any values that you previously edited in the CPC Configuration Editor. Values that you defined for the CPC override the updates.
- Based on the most recent cost model, Cost Analyzer updates the configuration only when:
- The CPC configuration does not yet exist.
- The CPC model does not exist in the current configuration.
- Preexisting CPCs in the CPC Configuration that no longer exist in the most recent Cost Model are not changed. These CPCs remain listed in the CPC Configuration Editor, but they are inactive and their parameters do not affect the costing data.