Country Multiplex Pricing (CMP), a new sub-capacity offering, enables more flexible deployment of workloads across all machines within a countryIBM Latin America Software Announcement LP15-0317
July 28, 2015
|Table of contents|
(Corrected on August 12, 2015)
A document name was corrected under "Terms and Conditions."
CMP is a new sub-capacity offering that allows clients to use their z Systems capacity within a given country without the constraints of sysplex aggregation rules and many of the limitations of previous reporting methodologies. This is a new way of measuring and pricing sub-capacity program MSUs that allows for more flexible deployment and movement of workloads across all machines within a country. A Multiplex is the collection of all eligible IBM z Systems machines or sysplexes or both within a single country, measured as one machine for purposes of software sub-capacity reporting. An update to the Sub-Capacity Reporting Tool (SCRT), SCRT V23 R10.0, will be made available to generate a Multiplex report providing sub-capacity program utilization peaks across all machines in the Multiplex simultaneously, as opposed to separate peaks by machine, which is how SCRT works in a non-Multiplex environment.
CMP also simplifies the process for software migrations with a shift from Single Version Charging (SVC) and limited migration windows, to Multiplex Version Measurement (MVM) reporting where there are no time constraints. In addition, the cost of growth per-MSU for a given sub-capacity program is based on the total reported Multiplex MSUs, which means any given sub-capacity program has a single price point for growth in the country regardless of where the workload runs.
Shifting to CMP brings flexibility, simplicity, and growth going forward. Selecting this offering transitions a client's existing pricing structure to the new model, which includes the establishment of an MLC and MSU baseline for each program. Clients should contact their sales team to help understand how the requirements for CMP can be met.
Back to top
In order to qualify for IBM z Systems Country Multiplex Pricing (CMP), clients must:
- Run z/OS® V1 (5694-A01), z/OS V2 (5650-ZOS), or z/TPF (5748-T15) operating systems, the eligible operating systems, on one or more eligible servers as defined in the section Determining eligibility for IBM z Systems Country Multiplex Pricing.
- Agree to the terms in the Attachment for IBM® Country Multiplex Pricing (Z126-6965).
- For existing sysplex clients, be in compliance with sysplex aggregation rules and have submitted a valid Sysplex Verification Package (SVP) within the last twelve months.
- Execute the transition process requirements as described in this announcement letter in the section Transitioning to CMP.
- Install and use the updated SCRT V23 R10.0, or later, on an IBM z Systems server according to the instructions and guidelines in the user guide. Starting with V23 R10.0 SCRT requires the IBM Runtime Environment, Java Technology Edition, Version 7.0, or later.
- Run SCRT for each sub-capacity reporting period and submit the resulting Multiplex report to IBM on a monthly basis.
Back to top
|Planned availability date|
October 2, 2015
Back to top
CMP is a new sub-capacity offering that simplifies multiple aspects of prior sub-capacity pricing structures with the objective of creating a flexible, country-wide z Systems platform where clients can configure and balance workloads more easily with fewer constraints. When eligibility requirements are met, as described in this announcement, clients can transition to this offering at any time after the Multiplex planned availability date. The following sections describe in detail all requirements, the initial transition process, changes to prior rules and guidelines, as well as how MSU peak calculations and monthly billing work under CMP.
Determining eligibility for IBM z Systems Country Multiplex Pricing
- General eligibility
Clients running eligible operating systems and hardware, either stand-alone machines or sysplexes, may implement CMP provided they satisfy all prerequisites and requirements as described in this announcement and in the Attachment for IBM Country Multiplex Pricing.
For any questions regarding eligibility, please contact your sales representative.
- Service providers
Clients acting as service providers, using z Systems software to host applications or infrastructure for a third party, may implement CMP only for eligible machines that are dedicated to a particular end-user client. Service providers implementing CMP may have one Multiplex (as defined below) per dedicated end-user client environment within a country. Multi-tenant (non-dedicated) machines or sysplexes are not eligible for CMP.
- Hardware eligibility
A Multiplex will consist of all eligible machines owned or leased by an Enterprise within a country. An Enterprise is any legal entity and the subsidiaries it owns by more than 50%. For clients not acting as service providers, all machines with an eligible operating system within an Enterprise in a given country (including all Capacity Back Up (CBU) machines available to be used by these machines) must be included in the Multiplex when a client first implements this offering. Clients may have only one Multiplex per country and a Multiplex may not span country borders.
Machines eligible to be included in a new Multiplex cannot be older than two generations prior to the most recently available server at the time a client first implements a Multiplex. The most recent server at any given point in time will be considered generation N, and the prior two N-1 and N-2 respectively. At the time of this announcement, the servers eligible for Multiplex that encompass these generations include z13 (generation N), zEC12 and zBC12 (generation N-1), and z196 and z114 (generation N-2) machine types 2964, 2827, 2828, 2817, and 2818, respectively.
Clients are not eligible for CMP until machines with eligible operating systems (along with any associated CBU machines) that are older than generation N-2 are upgraded, or that workload is transferred to eligible machines, or the older ineligible machines are converted to no longer run z/OS nor z/TPF software. Once a client establishes a Multiplex they may keep the machines originally included in their Multiplex indefinitely. Going forward, any machine to be added to an existing Multiplex must conform to the machine types that satisfy the generation N, N-1, and N-2 criteria at the time that machine is added.
The following types of servers will not be included in a Multiplex and will continue to be licensed, reported, and billed according to their applicable non-CMP terms:
- Cold Disaster Recovery (DR) machines that are not running any billable software
- Solution Edition machines
- Developer Discount machines
- Machines running only z/VSE®, z/VM®, or Linux
Operating system and software price metric eligibility
Machines with z/OS or z/TPF workloads or both are eligible for CMP. Machines running both z/VSE and z/OS may participate in a Multiplex but only the z/OS portion of that machine will be priced under CMP terms. z/VSE workloads will continue to be reported and priced according to announced stand-alone billing metrics. Similarly, machines that contain both Solution Edition (SE) workloads and standard z/OS or z/TPF workloads are eligible to participate in CMP, but only the non-SE workloads will be priced under CMP, since Solution Editions are considered separately priced full-capacity workloads. Multiplex reports must exclude the SE workloads.
While all existing pricing metrics for z/OS and z/TPF workloads are eligible to transition to CMP, there is a new pricing metric called Country Multiplex License Charges (CMLC) that will be used for all Multiplexes. In addition, a new Multiplex zNALC (MzNALC) metric will replace the original zNALC metric for use within a Multiplex. All sub-capacity eligible programs within a Multiplex must be priced according to CMLC or zNALC sub-capacity terms. Machines that are full capacity (such as PSLC) prior to CMP will be eligible for inclusion in a Multiplex but must transition to CMP sub-capacity terms. Clients still using the original NALC metric must adopt zNALC terms and conditions prior to the transition to CMP. Only the CMLC and MzNALC metrics will be supported on Multiplex machines for sub-capacity-eligible z/OS and z/TPF workloads.
In the case of IPLA programs, sub-capacity terms are not required. Detailed terms and conditions for IPLA programs running on Multiplex machines are described in the IPLA program terms in a Multiplex section of this announcement letter.
- Programs that are not eligible for sub-capacity
MLC charges for non-sub-capacity-eligible programs are calculated according to the announced pricing metric and terms for each given program. In the case of non-sub-capacity-eligible products that require the Fixed Workload License Charge (FWLC) or Tiered Workload License Charge (TWLC) metric and are installed on a zBC12 or z114 machine, they will use the appropriate TWLC metric while the machine is part of a Multiplex. This will also be true for future follow-on machines announced as eligible for TWLC.
- Sysplex environments
Clients with existing sysplexes that use sysplex aggregation pricing and are to become part of a Multiplex must be in compliance with announced sysplex rules prior to entering the Multiplex. Otherwise, the MLC Base will be calculated on a non-aggregated basis. Clients must have submitted a valid Sysplex Verification Package within the prior 12 months. Sysplex aggregation rules and related reporting requirements (SVP) are eliminated under CMP for clients who were sysplex compliant before entering CMP.
Country Multiplex License Charges (CMLC) and Multiplex zNALC (MzNALC) pricing metrics
Each CMLC-eligible and MzNALC-eligible software program has a monthly license charge based on a cumulative price structure with multiple levels. IBM is adding additional price metric tiers compared to previous metrics to provide additional price performance for growth under CMP.
CMLC and MzNALC metric tiers
|Base charge||Up to 3|
|Level 0||4 - 45|
|Level 1||46 - 175|
|Level 2||176 - 315|
|Level 3||316 - 575|
|Level 4||576 - 875|
|Level 5||876 - 1315|
|Level 6||1316 - 1975|
|Level 7||1976 - 2499|
|Level 8||2500 - 3499|
|Level 9||3500 - 4999|
|Level 10||5000 - 6999|
|Level 11||7000 - 9999|
|Level 12||10000 - 13999|
|Level 13||14000 or more|
Sub-capacity reporting in a Multiplex
Sub-Capacity Reporting Tool (SCRT)
Clients are required to install and use SCRT V23 R10.0, or later, in order to take advantage of CMP. Starting with V23 R10.0 SCRT requires the IBM Runtime Environment, Java Technology Edition, Version 7.0, or later. The updated version of SCRT is similar to prior versions except that it will have the capability to measure the 4-hour rolling average across all machines in a Multiplex as opposed to per individual machine. The tool, along with an updated SCRT Users Guide, will be available for download on October 2, 2015, at
The sub-capacity data capture requirements have also been modified for Multiplex reports compared to sub-capacity reports. No longer will a single "Percent Data Collected" figure be used for each operating system reported. In Multiplex reports, the missing data notifications will be more granular, identifying intervals when:
- LPARs have unmatched SMF 70 and SMF 89 records
- Active LPARs have no SMF nor SCRT89 records
- Machines have no SMF nor SCRT89 data from any LPAR
If any of these circumstances occur, the client will be required to explain the reason for the missing data when submitting their Multiplex report. Further details will be available in the SCRT Users Guide.
In addition, SCRT V23 R10.0 incorporates support for the following:
- Mobile Workload Pricing (MWP) for z/OS
Additional information on MWP can be found in Software Announcement LP14-0279, dated May 6, 2014.
Systems Collocated Application Pricing (zCAP)
Additional information on zCAP can be found in Software Announcement LP15-0243, dated April 7, 2015.
- Multiplex Version Measurement (MVM)
For additional information on MVM, refer to the Multiplex Version Measurement (MVM) replaces Single Version Charging (SVC) section.
Measurement and reporting of sub-capacity MSU peaks across a Multiplex
For each sub-capacity-eligible program running on a machine within the Multiplex, the 4-hour-rolling-average (4HRA) MSU peak value for the reporting period is determined according to the following methodology:
- SCRT uses SMF 70 or z/TPF SCRT89 records to determine the 4HRA MSU value by LPAR for each hourly interval.
- SCRT uses SMF 89 or z/TPF SCRT89 records or NO89 data to identify the LPAR(s) in which each sub-capacity-eligible program was running during each hourly interval.
- For each sub-capacity-eligible program, at each interval, SCRT adds the 4HRA MSU values for all LPARs in the Multiplex where the program was running in that interval.
- SCRT determines the highest 4HRA MSU value across all hourly intervals reported for each program during a given reporting period, to be used as the MSU peak value for that reporting period.
CMP clients are required to run SCRT V23 R10.0, or later, and submit a Multiplex report to IBM on a monthly basis in a manner similar to how sub-capacity reports are submitted.
In most countries, submission of sub-capacity reports is through the License Management Support (LMS) application, using either the LMS Web or LMS Email function. Initially, LMS Email support is not available for Multiplex report submission. CMP clients in countries where LMS is used are required to submit their Multiplex report using LMS Web.
Clients will be informed by an LMS Email subscription notification when their Multiplex report may be submitted using email. For more information about LMS Web, LMS Email, and the types of notifications available from LMS Email subscription, refer to
Transitioning to CMP
For clients with existing z Systems machines running billable software on eligible operating systems, a transition process is required to implement CMP. The transition process will include the creation of an MSU and MLC baseline according to the process and terms described in this announcement. Setting the bases is a one-time event. The bases do not represent fixed minimum values for billing purposes but rather reference points used to transition a client to the CMLC metric and CMP terms. There will be no retroactive application of CMP charges.
For new clients, or for new z Systems machines that represent a client's first installation in a given country, there will be no transition process. New environments will simply begin using SCRT to report sub-capacity MSUs on a Multiplex report and will be billed according to the terms and price points of the new CMLC metric without the need to establish an MLC and MSU baseline. The new machines will be billed on a full-capacity basis for the initial month and until the first valid SCRT report is generated and submitted for sub-capacity pricing.
Establishing the MSU Base for a program
Per CMP terms, SCRT will report the Multiplex peak MSUs across all machines in a country. The resulting Multiplex peak MSUs will typically be lower than, or in some cases equal to, the sum of the machine-peak MSUs reported by prior sub-capacity reports as generated by SCRT or the Mobile Workload Reporting Tool (MWRT) for the same billing period. Because of this change in reporting methodology, each sub-capacity program billable feature will have an MSU Base set according to a Multiplex peak measurement.
The Base will be the average of the Multiplex MSU peak for a given program for all machines to be included in the Multiplex, over the most recent three billing periods at the time a client implements a Multiplex. The process to establish the Base will be as follows:
- Clients must install SCRT V23 R10.0, or later, to generate the Multiplex reports that will be used to determine the MSU Bases.
- For each of the three billing periods, clients will collect all the SMF 70, SMF 89, and SCRT89 records for all machines in the Multiplex, load the files into SCRT, and generate a Multiplex report using the same EXCLUDE statements and other relevant sub-capacity reporting options, such as Mobile Workload Pricing (MWP) or Integrated Workload Pricing (IWP) where applicable, as were used when generating sub-capacity reports for those same periods. (Note that the SMF 70, SMF 89, and SCRT89 records are the standard data records required for prior versions of SCRT and MWRT.)
- The result will be one Multiplex report for each of the three billing periods, which will be validated against prior sub-capacity reports and approved for use by IBM.
- The average of the MSUs shown on these reports will be used to set the Bases for each sub-capacity program billable feature.
The MSU Bases do not represent minimum capacity levels, but rather reference points used to transition clients to the CMLC metric. Additional details on monthly billing are provided in the section Monthly charging for MLC programs.
Establishing the MLC Base and MLC Base Factor for a program
Each sub-capacity program billable feature will have an MLC Base. The Base will be the average of the most recent three billing periods of the total MLC billed for a given program using list prices, for all machines and sysplexes to be included in the Multiplex. Note: For clients with MLC software under the scope of an IBM Enterprise License Agreement, the MLC figures used to calculate the MLC Base will be the equivalent list prices for the MLC Inventory Values for the relevant reporting periods. The MLC Base will be used to transition clients to CMP at their current billing levels for the corresponding CMP MSU Base for a given program. The transition to CMP is not intended to reduce a client's MLC charges as calculated before CMP.
The MLC Base is then used to create an MLC Base Factor for each program that will be used going forward for monthly billing on CMLC. The MLC Base Factor will represent the difference between the MLC Base and the CMLC list price of the corresponding MSU Base for the same program. Any applicable Technology Transition Offering (TTO) reduction benefit will be included in all variables in the formula. See formula below:
MLC Base Factor = [MLC Base - (MSU Base@CMLC)] / [(MSU Base@CMLC)]
As noted above, the MLC Base Factor is necessary to transition a client to the new model at their current billing levels while allowing the Multiplex to simply be priced using the reported Multiplex peak MSUs for a given program on the CMLC curve each month. The MSU Base and MLC Base Factor for each program billable feature will be documented in a CMP contract supplement when a client first implements a Multiplex. For example:
|Program ID||Program Description||MSU Base||MLC Base Factor|
|5615-DB2||DB2® 11 for z/OS||x||x.x|
|5635-A04||IMS Transaction Manager V13||x||x.x|
|5650-ZOS||z/OS V2 Base||x||x.x|
|5650-ZOS||z/OS V2 DFSMS dsshsm||x||x.x|
|5650-ZOS||z/OS V2 DFSORT||x||x.x|
With the exception of special circumstances, the MLC Base Factors will be fixed values used to facilitate a client's transition to CMLC prices. Note that for all clients who implement a Multiplex prior to January 1, 2016, the initial MLC Base Factors established will be recalculated for January 1, 2016, in accordance with any price actions effective January 1, 2016. This is a one-time special situation due to the timing of these related pricing announcements.
Monthly charging for MLC programs
Once a client completes the initial transition requirements, the monthly pricing process is straightforward, similar to how AWLC sub-capacity pricing works today. All reported MSUs will be priced by program on CMLC as if they were in one country-wide sysplex, then IBM will apply the MLC Base Factor to calculate the final bill. The steps that will be followed to calculate MLC charges for a given sub-capacity program are as follows:
- Calculate the list price of the total reported Multiplex peak MSUs using the CMLC metric.
- Calculate the list price of the Base MSUs using the CMLC metric.
- Multiply #2 by the MLC Base Factor.
- Add the values in #1 and #3 to determine the CMLC price for that period.
Here is an example (figures are for illustrative purposes only):
A program has an MSU Base of 3,000 MSUs, an MLC Base of $211,000, and an MLC Base Factor of 2%. Actual reported MSUs for the given month are 3,500:
- First, the list price is calculated for the total 3,500 reported MSUs using the CMLC curve: $232,000
- Then, the CMLC price of the MSU Base of 3,000 MSUs is calculated: $207,000
- Next, the factor of 2% of the price of the MSU Base in #2 is applied: $207,000 x 2% = $4,140
- Finally, the monthly bill is the sum of #1 and #3: $232,000 + $4,140 = $236,140
The same process applies for the MzNALC metric if zNALC workloads are present.
By using a distinct Multiplex price curve (CMLC), all list price changes, as well as any applicable TTO benefits, are automatically applied to the MLC without need for a new process.
Technology Transition Offerings (TTOs)
When clients upgrade machines in a Multiplex, the TTOs announced with the given hardware generation will be used for CMP. A Multiplex will be considered a single sysplex for purposes of determining the level of pricing benefit applicable for a given machine upgrade and TTO.
CMP billing effective date
Sub-capacity licenses reflecting CMLC cannot be billed until the MSU Bases and MLC Base Factors are established and the client submits an SCRT Multiplex report, reflecting programs with MSUs in the new CMP structure. The SCRT V23 R10.0 with Multiplex functionality is planned to be available on October 2, 2015.
For example, if the first Multiplex billing date is November 1, 2015:
- The MLC Base will use the average of the August, September, and October billing amounts. In the case of ELAs, it will use the average of the MLC Inventory values for those same months.
- The MSU Base will use the average of the June, July, and August reporting periods which correspond to the August, September, and October billing periods; the client must generate the Multiplex reports for these periods.
- For the first Multiplex billing on November 1, the actual MSUs used will be from the Multiplex report containing data from the September reporting period (September 2 through October 1).
Multiplex Version Measurement (MVM) replaces Single Version Charging (SVC)
All Multiplexes that run multiple versions of a given sub-capacity-eligible program will now be measured and priced according to MVM terms. For clients running multiple versions of a given sub-capacity program, such as DB2 for z/OS, all MSUs for multiple versions within a given Program Family of Program IDs (PIDs) will be reported on a concurrent basis, similar to how SCRT measures z/OS today. SCRT will calculate the 4HRA for the concurrent peak (indicated by "(All)" in the report) by adding up the LPAR values where any version of the product is running. There are no time limits for version migration under CMP, so SVC terms do not apply under CMP. For billing purposes, all MSUs within a given family will be reported on a concurrent peak basis and priced at the cost of the latest version of the program within the family. Clients will essentially be paying for all instances of a program, such as DB2, reported as if it is a single version.
When first implementing CMP, if a client is running multiple versions of a sub-capacity-eligible program across the Multiplex machines, the reported concurrent peak for all versions (including those under SVC) will be used to establish the MSU Base for that Program Family. The MSU Base will be established under the latest version Program ID.
In the case of non-sub-capacity-eligible programs, such as flat-priced programs, clients who are running two versions before they enter the Multiplex but are only paying for one under SVC will continue to be charged for only that one under Multiplex without a migration time limit. Those that enter the Multiplex with one version and start migrating to a new version in the future will have to pay for both versions for as long as both continue to be used, regardless of whether the new version is incorporated into a sub-capacity-eligible program.
The tables in sections Programs eligible for CMLC with MLC Program Families under CMP and IPLA Execution-based Program Families under CMP show the programs and Program IDs that correspond to a given family for both MLC and IPLA programs. Program Family definitions will be updated as new versions are released.
IPLA program terms in a Multiplex
Migration of IPLA program versions
The previously announced migration grace period time limit of six months for IPLA program version migrations has been eliminated under CMP. Clients may run multiple program versions concurrently without additional charge so long as such aggregate use does not exceed that program's license entitlement. In addition, CMP clients will not be subject to the base IPLA contract terms that terminate the right to use the older version of a program when a more recent version is acquired with an upgrade or trade-up.
IPLA Execution-based programs
For IPLA Execution-based programs, the peak MSUs used for billing purposes will be the Multiplex MSU peak reported by SCRT for that program. For clients running multiple versions of a given program, SCRT will report an "(All)" line that shows the concurrent peak for all versions of the program running in the Multiplex. This single concurrent peak will be the MSU value used for collectively billing all versions running in the Multiplex, and will be priced using the price points of the most recent version installed.
IPLA z/OS-based programs
IPLA z/OS-based programs will continue to use the z/OS MSUs reported for the machines where they are running. The Multiplex report will show the contribution of each machine's MSUs to the overall Multiplex peak, and IBM will use the sum of those individual machine values as the MSUs for billing IPLA z/OS-based programs. In the case where SCRT reports both z/OS traditional and z/OS zNALC values for a given Multiplex, the sum of the traditional and zNALC MSUs will be the value used when calculating total MSUs for billing a z/OS-based program on a given machine or group of machines.
IPLA Reference-based programs
For IPLA Reference-based programs, which are priced according to the reported MSUs for a given parent program, the billing MSUs will have an Environment scope based upon an Establishment, as opposed to the previously used Environment scope of either a sysplex or a stand-alone server. An Establishment is defined as a single physical site, including the surrounding campus and satellite offices located within 50 kilometers of a client's site address. MSUs used for billing the IPLA program will be the sum of the MSUs reported by SCRT for the parent program (combined concurrent peak) for all machines that run in the same Establishment as the IPLA program. Note: The machine values will represent the contribution of each machine's MSUs to the overall Multiplex peak, as reported by SCRT, and not the individual machines' peaks.
Sub-capacity IPLA terms are not required under CMP. Clients who have not adopted IPLA sub-capacity may continue to maintain their existing full-capacity program entitlements.
Value Unit Edition (VUE) program terms in a Multiplex
Prior sub-capacity rules for VUE programs allowed for a technique called "pseudo-aggregation" where the reported MSUs of the corresponding version of the MLC program are added to the reported VUE program MSUs when calculating required Value Unit entitlements for a given VUE program on a stand-alone machine. For sysplexes, the MLC program MSUs used in the calculation are the total MLC program MSUs reported for all the machines in the sysplex where the VUE program runs. In a Multiplex, the MLC program MSUs to be used for any pseudo-aggregation calculation will simply be the Multiplex report concurrent peak MSUs for the MLC program.
Adding or removing programs or machines under CMP
CMP introduces changes in the way the software inventory is maintained and billed compared to the way it worked prior to Multiplex. The following sections describe how program and machine changes affect licensing and billing under CMP.
- Adding a new Program Family to the Multiplex
Any new sub-capacity-eligible program that is a member of a Program Family not previously licensed to any of the Multiplex machines will have an MLC Base Factor of 0 and an MSU Base of 3. Once the program is licensed to the machine, it will bill at the minimum 3 MSU price until it appears in the Multiplex report. Subsequent MLC charges for these programs (on the CMLC metric) will be based upon the reported MSUs for this Program Family on the Multiplex report.
- Adding a new program version within an existing Program Family
in the Multiplex
When a new version of a product within an existing Program Family is first licensed, the MLC Base Factor and MSU Base of the prior version are transferred to the new version. Program Family MSUs will then be billed against the new version.
- Adding a machine to an existing Multiplex
If a client adds a machine to a Multiplex, but does not change the programs installed in the Multiplex, then no adjustment is made to the MLC Bases or MSU Bases. Once the machine begins reporting MSUs in the Multiplex report, the incremental workload simply comes in as additional MSUs.
- Removing a Program Family from the Multiplex
If a program is permanently removed from the Multiplex, and no other versions within the same Program Family remain installed, then the MLC Base and MLC Base Factor for that program will be removed from inventory once the program's license is discontinued. If a program is removed from the Multiplex but other versions within the same Program Family remain installed, the inventory will simply be updated to reflect the removal of that particular program license.
- Removing a machine from a Multiplex or removing a program from
If a client decommissions a machine, migrates or upgrades to a new machine, or otherwise stops running a program on a machine, no adjustment is made to the MLC Base Factors or MSU Bases. The change will only impact the sub-capacity charges as measured by future months' SCRT Multiplex reporting.
The licenses on the machine will continue billing for as long as any MSUs appear in the Multiplex report, even if the client has asked to discontinue the licenses on the old machine. This is different from how sub-capacity licenses are handled outside of CMP, but it accounts for the fact that inside a Multiplex, a new machine comes in with 0 MSU registration licenses whereas outside of CMP a new machine comes in with full-capacity billing.
Programs eligible for CMLC with MLC Program Families under CMP
Note: Program eligibility is subject to product availability, including new programs that may become eligible for CMLC. For future updates see
|Software Offering (SWO)||Entitlement Entity (EE)||Description||Program Family name|
|5694-A01||S00T4FS||z/OS V1 Alternate Base||z/OS|
|5694-A01||S00T4FR||z/OS V1 Base||z/OS|
|5694-A01||S00T4FT||z/OS V1 BDT FTF||z/OS|
|5694-A01||S00T4FV||z/OS V1 BDT SNA NJE||z/OS|
|5694-A01||S00T4FW||z/OS V1 BookManager® Build||z/OS|
|5694-A01||S00T4FX||z/OS V1 C/C++ with Debug||z/OS|
|5694-A01||S00T4FZ||z/OS V1 C/C++ without Debug||z/OS|
|5694-A01||S00T4G2||z/OS V1 DFSMS dss||z/OS|
|5694-A01||S00T4G0||z/OS V1 DFSMS dsshsm||z/OS|
|5694-A01||S00T4G1||z/OS V1 DFSMS rmm||z/OS|
|5694-A01||S010776||z/OS V1 DFSMStvs||z/OS|
|5694-A01||S00T4G3||z/OS V1 DFSORT||z/OS|
|5694-A01||S00T4G4||z/OS V1 GDDM-PGF||z/OS|
|5694-A01||S00T4G5||z/OS V1 GDDM-REXX||z/OS|
|5694-A01||S00T4G8||z/OS V1 Infoprint Server||z/OS|
|5694-A01||S00T4G9||z/OS V1 JES3||z/OS|
|5694-A01||S00T4GB||z/OS V1 RMF||z/OS|
|5694-A01||S00T4GC||z/OS V1 SDSF||z/OS|
|5694-A01||S00T4GF||z/OS V1 Security Server||z/OS|
|5694-A01||S00T4GD||z/OS V1 SOMobjects® ADE||z/OS|
|5650-ZOS||S01728S||z/OS V2 Alternate Base||z/OS|
|5650-ZOS||S01728T||z/OS V2 Base||z/OS|
|5650-ZOS||S01728V||z/OS V2 BDT FTF||z/OS|
|5650-ZOS||S01728W||z/OS V2 BDT SNA NJE||z/OS|
|5650-ZOS||S01728X||z/OS V2 BookManager Build||z/OS|
|5650-ZOS||S017290||z/OS V2 DFSMS dss||z/OS|
|5650-ZOS||S017291||z/OS V2 DFSMS dsshsm||z/OS|
|5650-ZOS||S017292||z/OS V2 DFSMS rmm||z/OS|
|5650-ZOS||S017293||z/OS V2 DFSMStvs||z/OS|
|5650-ZOS||S017294||z/OS V2 DFSORT||z/OS|
|5650-ZOS||S017295||z/OS V2 GDDM-PGF||z/OS|
|5650-ZOS||S017296||z/OS V2 GDDM-REXX||z/OS|
|5650-ZOS||S017297||z/OS V2 HCM||z/OS|
|5650-ZOS||S017298||z/OS V2 HLASM Toolkit||z/OS|
|5650-ZOS||S017299||z/OS V2 Infoprint Server||z/OS|
|5650-ZOS||S01729B||z/OS V2 JES3||z/OS|
|5650-ZOS||S01729C||z/OS V2 RMF||z/OS|
|5650-ZOS||S01729D||z/OS V2 SDSF||z/OS|
|5650-ZOS||S01729F||z/OS V2 Security Server||z/OS|
|5650-ZOS||S01728Z||z/OS V2 XL C/C++||z/OS|
|5650-ZOS||S01780D||z/OS V2 zEDC||z/OS|
|5645-005||S000V5N||System Automation for OS/390®||System Automation|
|5645-006||S00SNWR||SA OS/390 V2||System Automation|
|5655-B22||S00S8F4||VA PL/I for OS/390 Alt Funct||PL/I|
|5655-B22||S00S8F5||VA PL/I for OS/390 Ful Funct||PL/I|
|5655-H31||S00W184||Enterprise PL/I Alt. Function||PL/I|
|5655-H31||S00W183||Enterprise PL/I Full Function||PL/I|
|5655-W67||S0166DJ||Enterprise PL/I for z/OS||PL/I|
|5697-B82||S001FFC||Tivoli® NetView® Enterprise||NetView|
|5697-B82||S001FFF||Tivoli NetView Procedural||NetView|
|5697-B82||S001FFD||Tivoli NetView Unattended||NetView|
|5697-ENV||S00WM20||IBM Tivoli NetView for z/OS||NetView|
|5697-ENV||S0148PZ||NetView for z/OS - TEMA||NetView|
|5697-NV6||S016RPV||IBM Tivoli NetView for z/OS||NetView|
|5697-NV6||S016RPM||NetView for z/OS - TEMA||NetView|
|5695-137||S000PX4||MQSeries® MVS/ESA||MQ for z/OS|
|5695-137||S000PX3||MQSeries for MVS/ESA Client Attachment Feature||MQ for z/OS|
|5655-A95||S00NB8L||MQSERIES FOR OS/390 V.2.1||MQ for z/OS|
|5655-A95||S00NB8K||MQSERIES V.2.1Client Attachment||MQ for z/OS|
|5655-F10||S00TDF5||WebSphere® MQ for z/OS||MQ for z/OS|
|5655-F10||S00TDFD||WebSphere MQ Client Attachments||MQ for z/OS|
|5697-MQZ||S010N7W||IBM Web MQ Ext Sec Ed z/OS||MQ for z/OS|
|5697-MQZ||S010N7T||Web MQ Client Attach Feature||MQ for z/OS|
|5655-L82||S011P8R||WebSphere MQ for z/OS||MQ for z/OS|
|5655-L82||S011P8T||WebSphere MQ V6 Client Attachment||MQ for z/OS|
|5697-NQZ||S012B7X||MQ Extended Security Edition||MQ for z/OS|
|5697-NQZ||S012B80||MQ Ext Client Attach Feat||MQ for z/OS|
|5655-R36||S014V9Z||WS MQ Base for z/OS||MQ for z/OS|
|5655-R36||S014VB0||WS MQ Client Attachment||MQ for z/OS|
|5655-W97||S017F7P||IBM WMQ for z/OS||MQ for z/OS|
|5799-GKY||S00TN86||MQS for OS/390 - Base||MQ for z/OS|
|5655-B86||S00RXVG||Lotus® Domino® for S/390®||Lotus Domino|
|5655-K36||S00XJ4K||Lotus Domino for z/OS V6||Lotus Domino|
|5655-N14||S011DT8||Lotus Domino for z/OS V7||Lotus Domino|
|5655-S73||S0144DV||Lotus Domino for z/OS||Lotus Domino|
|5695-176||S00150G||IMS/ESA® V5 Database Manager||IMS|
|5695-176||S00150J||IMS/ESA V5 DB Level Tracking||IMS|
|5695-176||S00150H||IMS/ESA V5 Ext. Terminal Opt||IMS|
|5695-176||S00150F||IMS/ESA V5 RSR-RLT||IMS|
|5695-176||S00150K||IMS/ESA V5 Surveyor Feature||IMS|
|5695-176||S00150D||IMS/ESA V5 Transaction Mgr.||IMS|
|5655-158||S001CFP||IMS/ESA V6 Database Manager||IMS|
|5655-158||S001CFS||IMS/ESA V6 DB Level Tracking||IMS|
|5655-158||S001CFR||IMS/ESA V6 Ext Terminal Opt||IMS|
|5655-158||S001CFN||IMS/ESA V6 RC Level Tracking||IMS|
|5655-158||S001CFT||IMS/ESA V6 Transaction Mgr||IMS|
|5655-B01||S00TBG7||IMS V7 Database Manager||IMS|
|5655-B01||S00TBG6||IMS V7 Extended Terminal Opt||IMS|
|5655-B01||S00TBG9||IMS V7 RSR DB Level Tracking||IMS|
|5655-B01||S00TBG8||IMS V7 RSR RC Level Tracking||IMS|
|5655-B01||S00TBGB||IMS V7 Transaction Manager||IMS|
|5655-C56||S00W276||IMS V8 Database Manager||IMS|
|5655-C56||S00W275||IMS V8 DB-Level Tracking||IMS|
|5655-C56||S00W277||IMS V8 Extended Terminal Opt||IMS|
|5655-C56||S00W278||IMS V8 Recov Lvl Tracking||IMS|
|5655-C56||S00W274||IMS V8 Transaction Manager||IMS|
|5655-J38||S0108VK||IMS V9 Database Manager||IMS|
|5655-J38||S0108VM||IMS V9 DB-Level Tracking||IMS|
|5655-J38||S0108VP||IMS V9 Extended Terminal Opt||IMS|
|5655-J38||S0108VS||IMS V9 Recov Lvl Tracking||IMS|
|5655-J38||S0108VV||IMS V9 Transaction Manager||IMS|
|5635-A01||S012K9W||IMS V10 Database Manager||IMS|
|5635-A01||S012K9X||IMS V10 DB-Level Tracking||IMS|
|5635-A01||S012KB0||IMS V10 Extended Term Opt||IMS|
|5635-A01||S012K9Z||IMS V10 Recov Lvl Tracking||IMS|
|5635-A01||S012K9B||IMS V10 Transaction Manager||IMS|
|5635-A02||S0152Z1||IMS Database Manager||IMS|
|5635-A02||S0152Z2||IMS DB-Level Tracking||IMS|
|5635-A02||S0152XX||IMS Extended Term Opt||IMS|
|5635-A02||S0152XZ||IMS Recov Lvl Tracking||IMS|
|5635-A02||S0152Z0||IMS Transaction Manager||IMS|
|5635-A03||S0166J4||IMS V12 Database Manager||IMS|
|5635-A03||S0166J5||IMS V12 DB-Level Tracking||IMS|
|5635-A03||S0166J1||IMS V12 Extended Term Opt||IMS|
|5635-A03||S0166J2||IMS V12 Recov Lvl Tracking||IMS|
|5635-A03||S0166J3||IMS V12 Transaction Manager||IMS|
|5635-A04||S0171RS||IMS Database Manager V13||IMS|
|5635-A04||S0171RT||IMS DB-Level Tracking V13||IMS|
|5635-A04||S0171RV||IMS Extended Term Opt V13||IMS|
|5635-A04||S0171RW||IMS Recov Lvl Tracking V13||IMS|
|5635-A04||S0171RX||IMS Transaction Manager V13||IMS|
|5635-A05||S017K88||IMS Database Mgr V14||IMS|
|5635-A05||S017K89||IMS DB-Lvl Tracking V14||IMS|
|5635-A05||S017K8B||IMS ETO V14||IMS|
|5635-A05||S017K8C||IMS Recov Lvl Track V14||IMS|
|5635-A05||S017K8D||IMS Transaction Mgr V14||IMS|
|5655-H32||S00X8FN||Debug Tool for z/OS & OS/390||Debug Tool|
|5655-L24||S0109LN||Debug Tool V4||Debug Tool|
|5655-M18||S011CMT||Debug Tool V5||Debug Tool|
|5655-P14||S0121TL||Debug Tool V6||Debug Tool|
|5655-R44||S012PVX||Debug Tool V7||Debug Tool|
|5655-S17||S01489W||Debug Tool V8||Debug Tool|
|5695-DB2||S00184N||DB2 for MVS/ESA V4||DB2 for z/OS|
|5655-DB2||S001FJ7||IBM DB2 for OS/390 Version 5||DB2 for z/OS|
|5655-DB2||S001FJ8||DB2 V5 Performance Monitor||DB2 for z/OS|
|5655-DB2||S00MVJ2||QMF Win V6 F/C of DB2 V5||DB2 for z/OS|
|5655-DB2||S00MVJ4||QMF Win V6 w Host QMF prereq||DB2 for z/OS|
|5645-DB2||S00087N||DB2 UDB for OS/390||DB2 for z/OS|
|5645-DB2||S00V5XB||Net Search Extender||DB2 for z/OS|
|5645-DB2||S00087P||QMF for OS/390||DB2 for z/OS|
|5645-DB2||S00VWVP||QMF for OS/390 Version 7||DB2 for z/OS|
|5645-DB2||S00VWVT||QMF for Win V7 (Feat of DB2)||DB2 for z/OS|
|5645-DB2||S00VWVW||QMF for Win V7 (Feat of QMF)||DB2 for z/OS|
|5645-DB2||S00087M||QMF for Windows w/QMF Lic||DB2 for z/OS|
|5645-DB2||S00087J||QMF for Windows-No QMF Lic.||DB2 for z/OS|
|5645-DB2||S00087G||QMF HPO Buy||DB2 for z/OS|
|5645-DB2||S00VWVZ||QMF HPO Version 7||DB2 for z/OS|
|5675-DB2||S00SN65||DB2 UDB for OS/390||DB2 for z/OS|
|5675-DB2||S00TZJH||DB2 Net Search Extender||DB2 for z/OS|
|5675-DB2||S00SN6L||DB2 Warehouse Manager||DB2 for z/OS|
|5675-DB2||S00SN6M||QMF for OS/390 (feat of DB2)||DB2 for z/OS|
|5675-DB2||S00SN6X||QMF for Windows feat of DB2||DB2 for z/OS|
|5675-DB2||S00SN6S||QMF for Windows feat of QMF||DB2 for z/OS|
|5675-DB2||S00VWTB||QMF HPO Version 7.1.1||DB2 for z/OS|
|5625-DB2||S00X44M||DB2 UDB for z/OS||DB2 for z/OS|
|5625-DB2||S010TGB||DB2 Net Search Extender||DB2 for z/OS|
|5625-DB2||S00X44R||QMF Classic Edition||DB2 for z/OS|
|5625-DB2||S00X44P||QMF Distributed Edition||DB2 for z/OS|
|5625-DB2||S00X44N||QMF Enterprise Edition||DB2 for z/OS|
|5635-DB2||S011XS0||DB2 V9 for z/OS||DB2 for z/OS|
|5635-DB2||S012J7R||QMF Classic Edition||DB2 for z/OS|
|5635-DB2||S015SLK||QMF Classic Edition: V10||DB2 for z/OS|
|5635-DB2||S012J7P||QMF Enterprise Edition||DB2 for z/OS|
|5635-DB2||S015SLL||QMF Enterprise Edition: V10||DB2 for z/OS|
|5605-DB2||S015SW2||DB2 10 for z/OS||DB2 for z/OS|
|5605-DB2||S015SW4||QMF Classic Edition V10||DB2 for z/OS|
|5605-DB2||S015SW3||QMF Enterprise Edition V10||DB2 for z/OS|
|5605-DB2||S017HFV||QMF V11 Classic Edition||DB2 for z/OS|
|5605-DB2||S017HFT||QMF V11 Enterprise Edition||DB2 for z/OS|
|5615-DB2||S0171R2||DB2 11 for z/OS||DB2 for z/OS|
|5615-DB2||S0171R3||QMF Classic Edition V11||DB2 for z/OS|
|5615-DB2||S0171R4||QMF Enterprise Edition V11||DB2 for z/OS|
|5648-A25||S001FGK||COBOL for OS/390 & VM V2-Alt||COBOL|
|5648-A25||S001FGH||COBOL for OS/390 & VM V2||COBOL|
|5655-G53||S00VXNN||COBOL Alternate Function||COBOL|
|5655-G53||S00VXNM||COBOL Full Function||COBOL|
|5655-W32||S0177FX||Enterprise COBOL for z/OS V5||COBOL|
|5655-018||S00151M||CICS ONC RPC||CICS|
|5655-147||S001CVJ||CICS TS for OS/390||CICS|
|5697-E93||S00T7FK||CICS TS for z/OS V2||CICS|
|5655-M15||S0118T7||CICS TS for z/OS V3.2||CICS|
|5655-S97||S015H9T||CICS TS for z/OS||CICS|
|5655-Y04||S0172DF||CICS TS for z/OS||CICS|
|5655-043||S00135C||Netview Perf Mon||N/A|
|5695-068||S000BKC||Airline Control System V2||N/A|
|5706-254||S00066K||QMF MVS Version 3||N/A|
|5706-254||S00066G||QMF for Windows||N/A|
|5655-P97||S01243R||Encryption Facil Encrypt Ser||N/A|
|5655-P97||S01256T||Encryption Facil dss Encrypt||N/A|
|5697-OPC||S001FDX||OPC 2.3 Tracker||N/A|
|5697-OPC||S001FDW||OPC Agent & Enabler||N/A|
|5697-OPC||S001FDV||OPC Controller Comm + Lang||N/A|
|5697-WSZ||S00W0CV||TWS Engine + Lang||N/A|
|5697-WSZ||S00W0CT||TWS for z/OS Agent||N/A|
|5697-WSZ||S00W0CW||TWS for z/OS END2END Enabler||N/A|
|5748-F15||S011DWP||z/TPF DF V1||N/A|
|5748-T15||S011DWM||z/TPF EE V1 HPO||N/A|
IPLA Execution-based Program Families under CMP
Note: Program eligibility is subject to product availability, including new programs that may be announced. For future updates see
|Software Offering (SWO)||Description||Program Family name|
|5697-H63||Application Monitor V1||Application Monitor|
|5655-L22||Application Monitor V2||Application Monitor|
|5697-N37||Application Performance Analyzer V1||App Performance Analyzer|
|5697-N53||Application Performance Analyzer V7||App Performance Analyzer|
|5697-N63||Application Performance Analyzer V8||App Performance Analyzer|
|5697-P10||Application Performance Analyzer for z/OS V9||App Performance Analyzer|
|5697-P36||Application Performance Analyzer for z/OS V10||App Performance Analyzer|
|5697-Q03||Application Performance Analyzer for z/OS V11||App Performance Analyzer|
|5655-W71||Application Performance Analyzer for z/OS V12||App Performance Analyzer|
|5655-Q09||Application Performance Analyzer for z/OS V13||App Performance Analyzer|
|5722-DFJ||CICS TS VUE V5||CICS TS VUE|
|5697-G57||Cloud 9 for SCLM for OS/390||Cloud 9 for SCLM|
|5655-G93||Cloud 9 for SCLM for z/OS||Cloud 9 for SCLM|
|5655-U99||Cognos® BI for z/OS V8||Cognos BI|
|5655-Y26||Cognos BI for z/OS V10||Cognos BI|
|5697-N29||DB2 8 for z/OS VUE||DB2 VUE|
|5697-P12||DB2 9 for z/OS VUE||DB2 VUE|
|5697-P31||DB2 10 for z/OS VUE||DB2 VUE|
|5697-P43||DB2 11 for z/OS VUE||DB2 VUE|
|5655-J18||Debug Tool Utils z/OS OS/390||Debug Tool|
|5655-L23||Debug Tool Utils & AF V4||Debug Tool|
|5655-M19||Debug Tool Utils & AF V5||Debug Tool|
|5655-P15||Debug Tool Utils & AF V6||Debug Tool|
|5655-R45||Debug Tool Utils & AF V7||Debug Tool|
|5655-S16||Debug Tool Utils & AF V8||Debug Tool|
|5655-U27||Debug Tool for z/OS V9||Debug Tool|
|5655-V50||Debug Tool for z/OS V10||Debug Tool|
|5655-W45||Debug Tool for z/OS V11||Debug Tool|
|5655-W70||Debug Tool for z/OS V12||Debug Tool|
|5655-Q10||Debug Tool for z/OS V13||Debug Tool|
|5697-F19||Fault Analyzer OS/390||Fault Analyzer|
|5655-G74||Fault Analyzer V2||Fault Analyzer|
|5655-J47||Fault Analyzer z/OS OS/390||Fault Analyzer|
|5655-L25||Fault Analyzer V4||Fault Analyzer|
|5655-M20||Fault Analyzer V5||Fault Analyzer|
|5655-P16||Fault Analyzer for z/OS V6||Fault Analyzer|
|5655-R46||Fault Analyzer V7||Fault Analyzer|
|5655-S15||Fault Analyzer V8||Fault Analyzer|
|5655-U28||Fault Analyzer for z/OS V9||Fault Analyzer|
|5655-V51||Fault Analyzer for z/OS V10||Fault Analyzer|
|5655-W46||Fault Analyzer for z/OS V11||Fault Analyzer|
|5655-W69||Fault Analyzer for z/OS V12||Fault Analyzer|
|5655-Q11||Fault Analyzer for z/OS V13||Fault Analyzer|
|5697-F20||File Manager for OS/390||File Manager|
|5655-G75||File Manager V2||File Manager|
|5655-J48||File Manager z/OS OS/390||File Manager|
|5655-L26||File Manager V4||File Manager|
|5655-M21||File Manager V5||File Manager|
|5655-P17||File Analyzer for z/OS V6||File Manager|
|5655-R47||File Manager V7||File Manager|
|5655-S14||File Manager V8||File Manager|
|5655-U29||File Manager for z/OS V9||File Manager|
|5655-V52||File Manager for z/OS V10||File Manager|
|5655-W47||File Manager for z/OS V11||File Manager|
|5655-W68||File Manager for z/OS V12||File Manager|
|5655-Q12||File Manager for z/OS V13||File Manager|
|5655-W11||WebSphere Business Monitor V7||IBM Business Monitor|
|5655-W96||IBM Business Monitor for z/OS V8||IBM Business Monitor|
|5655-N53||WebSphere Process Server for z/OS V6||IBM Business Process Manager|
|5655-W05||IBM Business Process Manager for z/OS V7||IBM Business Process Manager|
|5655-Y02||IBM Business Process Manager for z/OS V8||IBM Business Process Manager|
|5655-I58||Integrator Broker for z/OS||IBM Integration Bus|
|5655-K60||WBI Message Broker for z/OS||IBM Integration Bus|
|5655-M74||WebSphere Message Broker for z/OS V6||IBM Integration Bus|
|5655-V60||WebSphere Message Broker for z/OS V7||IBM Integration Bus|
|5697-P44||WebSphere Message Broker for z/OS V8||IBM Integration Bus|
|5655-IBB||IBM Integration Bus for z/OS V9||IBM Integration Bus|
|5655-AB1||IBM Integration Bus for z/OS V10||IBM Integration Bus|
|5655-IBC||IBM Integration Bus Standard Edition for z/OS V9||IBM Integration Bus SE|
|5655-AB2||IBM Integration Bus Standard Edition for z/OS V10||IBM Integration Bus SE|
|5655-U24||IBM Multi-site Workload Lifeline V1||IBM Multi-site Workload Lifeline|
|5655-UM4||IBM Multi-site Workload Lifeline V2||IBM Multi-site Workload Lifeline|
|5655-AA6||IBM SPSS® Modeler with Scoring Adapter for zEnterprise® V15||IBM SPSS Modeler|
|5655-AA8||IBM SPSS Modeler with Scoring Adapter for zEnterprise V16||IBM SPSS Modeler|
|5655-SP7||IBM SPSS Modeler Gold with Scoring adapter for z Systems V17||IBM SPSS Modeler|
|5655-DSQ||IMS DB VUE V12||IMS DB VUE|
|5655-DSM||IMS DB VUE V13||IMS DB VUE|
|5655-TM1||IMS TM VUE V12||IMS TM VUE|
|5655-TM2||IMS TM VUE V13||IMS TM VUE|
|5655-I18||Migration Utility V1||Migration Utility|
|5697-I89||Migration Utility V2||Migration Utility|
|5697-N44||Migration Utility for z/OS V3||Migration Utility|
|5655-MGU||Migration Utility for z/OS V4||Migration Utility|
|5655-VUE||WebSphere MQ for z/OS VUE V7||MQ for z/OS VUE|
|5655-VU8||WebSphere MQ for z/OS VUE V8||MQ for z/OS VUE|
|5655-U93||Data Studio pureQuery® Runtime for z/OS V1||Optim pureQuery Runtime|
|5655-V57||Data Studio pureQuery Runtime for z/OS V2||Optim pureQuery Runtime|
|5655-V80||Optim pureQuery Runtime for z/OS V2||Optim pureQuery Runtime|
|5655-W92||Optim pureQuery Runtime for z/OS V3||Optim pureQuery Runtime|
|5655-I49||WebSphere Studio Asset Analyzer V2||Rational® Asset Analyzer|
|5655-L21||WebSphere Studio Asset Analyzer V3||Rational Asset Analyzer|
|5655-M22||WebSphere Studio Asset Analyzer V4||Rational Asset Analyzer|
|5655-R10||WebSphere Studio Asset Analyzer V5||Rational Asset Analyzer|
|5655-W57||IBM Rational Asset Analyzer V6||Rational Asset Analyzer|
|5655-L03||SCLM Administrator Workbench z/OS||SCLM Administrator Toolkit|
|5697-J19||SCLM Administrator Toolkit V2||SCLM Administrator Toolkit|
|5697-N51||SCLM Administrator Toolkit V3||SCLM Administrator Toolkit|
|5697-N68||SCLM Administrator Toolkit for z/OS V4||SCLM Administrator Toolkit|
|5655-U74||SCLM Administrator Toolkit for z/OS V5||SCLM Administrator Toolkit|
|5655-M99||SCLM Developer's Toolkit||SCLM Developer Toolkit|
|5655-R37||SCLM Developer Toolkit V2||SCLM Developer Toolkit|
|5655-S72||SCLM Developer Toolkit V3||SCLM Developer Toolkit|
|5698-A71||IBM Tivoli Composite Application Manager for WebSphere||Tivoli Composite Application Manager|
|5698-B48||Tivoli Composite Application Manager for Appl Diag V7||Tivoli Composite Application Manager|
|5698-A10||Tivoli Mon for Net Perf||Tivoli Monitor for Network Performance|
|5698-FNP||Tivoli Monitor for Network Performance||Tivoli Monitor for Network Performance|
|5698-A87||IBM Tivoli OMEGAMON® XE for Messaging||Tivoli OMEGAMON XE for Messaging|
|5698-B23||Tivoli OMEGAMON XE for Messaging for z/OS V7||Tivoli OMEGAMON XE for Messaging|
|5698-Z01||Tivoli Storage Manager for z/OS Media V6||Tivoli Storage Manager|
|5698-AAH||Tivoli Storage Manager for z/OS Media V7||Tivoli Storage Manager|
|5698-Z02||Tivoli Storage Manager Extended Edition for z/OS Media V6||Tivoli Storage Manager EE|
|5698-AAK||Tivoli Storage Manager Extended Edition for z/OS Media V7||Tivoli Storage Manager EE|
|5698-A14||Tivoli System Automation||Tivoli System Automation|
|5698-SA3||IBM Tivoli System Automation for z/OS||Tivoli System Automation|
|5698-A17||Tivoli Workload Scheduler||Tivoli Workload Scheduler|
|5698-T08||Tivoli Workload Scheduler for z/OS V9||Tivoli Workload Scheduler|
|5655-F31||WebSphere Application Server for z/OS V4||WebSphere Application Server|
|5655-I35||WebSphere Application Server for z/OS V5||WebSphere Application Server|
|5655-N01||WebSphere Application Server for z/OS V6||WebSphere Application Server|
|5655-N02||WebSphere Application Server for z/OS V7||WebSphere Application Server|
|5655-W65||WebSphere Application Server for z/OS V8||WebSphere Application Server|
|5655-V54||WebSphere Business Events V6||WS Business Events|
|5655-W16||WebSphere Business Events for z/OS V7||WS Business Events|
|5655-ILG||WebSphere ILOG® Business Rules for z/OS V7||WS Business Rules|
|5655-Y31||WebSphere Business Rules for z/OS V8||WS Business Rules|
|5655-S30||WebSphere Business Services Fabric||WS Business Services Fabric|
|5655-W06||WebSphere Business Services Fabric for z/OS V7||WS Business Services Fabric|
|5655-R15||WebSphere Enterprise Service Bus for z/OS V6||WS Enterprise Service Bus|
|5655-W09||WebSphere Enterprise Service Bus for z/OS V7||WS Enterprise Service Bus|
|5655-K57||WBI Event Broker for z/OS||WS Event Broker|
|5655-M75||WebSphere Event Broker for z/OS||WS Event Broker|
|5655-V66||WebSphere eXtreme Scale z/OS||WS eXtreme Scale|
|5655-VX8||WebSphere eXtreme Scale for z/OS V8||WS eXtreme Scale|
|5655-G97||WebSphere MQ Integrator z/OS V2.1||WS Message Broker|
|5697-I11||WBI MB with R&F Extension||WS Message Broker|
|5697-J09||WebSphere Message Broker with R&F for z/OS||WS Message Broker|
|5655-W98||WebSphere MQ Advanced for z/OS V7||WS MQ Advanced for z/OS|
|5655-ADV||IBM WebSphere MQ Advanced z/OS||WS MQ Advanced for z/OS|
|5655-W50||WebSphere MQ Adv Message Security for z/OS V7||WS MQ Advanced Message Security|
|5655-AMS||IBM Websphere AMS for z/OS||WS MQ Advanced Message Security|
|5655-Y07||WebSphere Operational Decision Management for z/OS V7||WS Operational Decision Management|
|5655-Y17||WebSphere Operational Decision Management for z/OS V8||WS Operational Decision Management|
|5655-K12||Portal for z/OS & OS/390||WS Portal Enable|
|5655-M44||WebSphere Portal Enable z/OS||WS Portal Enable|
|5655-R17||WebSphere Portal Enable z/OS, V6||WS Portal Enable|
|5655-W49||WebSphere Portal Enable for z/OS V7||WS Portal Enable|
|5655-Y16||WebSphere Portal Enable for z/OS V8||WS Portal Enable|
|5655-R41||WebSphere Serv Reg & Rep'tory, V6||WS Service Registry & Repository|
|5655-W17||WebSphere Service Registry & Repository V7||WS Service Registry & Repository|
|5655-WBS||WebSphere Service Registry & Repository for z/OS V8||WS Service Registry & Repository|
|5655-J67||WebS Studio App Monitor zOS||WS Studio Application Monitor|
|5655-L42||WebS Studio Appli Monitor||WS Studio Application Monitor|
|5697-J18||WebSphere Studio Application Monitor||WS Studio Application Monitor|
|5655-L50||CICS Data Collector for WSAM||WSAM Data Collector for CICS|
|5697-J17||WSAM Data Collector for CICS||WSAM Data Collector for CICS|
|5655-T11||zSecure Alert||zSecure Alert|
|5655-N21||zSecure Alert V2||zSecure Alert|
|5655-T05||zSecure CICS Toolkit||zSecure CICS Toolkit|
|5655-N18||zSecure CICS Toolkit V2||zSecure CICS Toolkit|
Terms and Conditions
The client's agreement to Country Multiplex Pricing terms and conditions is required for the receipt of CMP benefits. Clients must have a valid license to authorized IBM z Systems CMLC or MzNALC programs installed on qualified z13, zEC12, zBC12, z196, z114, or future follow on servers that have implemented sub-capacity pricing. All terms and conditions associated with CMP sub-capacity pricing, and the IBM Client Agreement (or equivalent) apply.
Clients are required to:
- Collect SMF and SCRT89 data required by the SCRT and retain that data for a period of not less than six months.
- Submit Multiplex reports from the most current version of SCRT with complete data for all LPARs on all machines for the entire reporting period to IBM no later than the 9th day of the submission month. Multiplex reports that reflect a changed product MSU level or a change to the program inventory on any machine will be considered to be orders placed by the client without further action on the client's part and IBM is authorized to make any resulting billing increase or decrease. To place an order for a new license, or to discontinue licenses, move licenses between machines, report a hardware model upgrade or downgrade, or enable or disable product features, the client must contact IBM or their IBM Business Partner.
- Configure all machines in the Multiplex to send weekly Transmit System Availability Data (TSAD) to IBM via the IBM z Systems Remote Support Facility (RSF). If the machine cannot connect via the RSF, provide this TSAD via an alternate means documented in the SCRT Users Guide.
- Configure all machines in the Multiplex with Global Performance Data Control Authority as documented in the appropriate PR/SM Planning Guide for that machine.
The following documents are new for CMP:
- IBM Attachment
for Country Multiplex Pricing (Z126-6965)
- Required for clients to be eligible for CMP
- IBM Supplement
for Country Multiplex Pricing (Z126-6966)
- Required to establish the MSU Bases and MLC Base Factors upon entry into CMP
- IBM Amendment
to the Attachment for zNALC License Charges on IBM System
- Optional, but required for zNALC clients to be eligible for CMP
- IBM Amendment
for Sub-Capacity for One-Time Charge Programs with Country Multiplex
- Optional, but required for CMP clients to be eligible for IPLA sub-capacity
Additional zNALC terms and conditions described in the following documents apply for zNALC clients:
- IBM Attachment for zNALC License Charges on IBM System z (Z125-7454)
- IBM Exhibit for zNALC License Charges on IBM System z (Z125-7455)
Cancellation of Multiplex terms
A client may switch from CMP back to standard non-Multiplex pricing at any time. Such clients would be required to meet all applicable licensing terms, including standard sysplex aggregation rules and standard sub-capacity rules if requested. If participation in the CMP offering is terminated, a client may not resume participation in CMP for 12 months.
Back to top
|Statement of general direction|
IBM intends to make CMP available to US Government customers at a future date.
IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.
Back to top
For a list of software programs that are eligible for CMLC, refer to the Programs eligible for CMLC with MLC Program Families under CMP section in this announcement.
For information about machine exhibits, visit the Mainframe Exhibits section of the z Systems Software Contracts website at
z Systems, IBM z Systems, z13, IMS, RMF, QMF, MVS, Optim, zSecure and PR/SM are trademarks of IBM Corporation in the United States, other countries, or both.
IBM, z/OS, System z, z/VSE, z/VM, DB2, BookManager, SOMobjects, OS/390, Tivoli, NetView, MQSeries, WebSphere, Lotus, Domino, S/390, IMS/ESA, CICS, Cognos, SPSS, zEnterprise, pureQuery, Rational, OMEGAMON and ILOG are registered trademarks of IBM Corporation in the United States, other countries, or both.
Oracle and Java are trademarks of Oracle and/or its affiliates in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Windows is a trademark of Microsoft Corporation in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks of others.
For the most current information regarding IBM products, consult your IBM representative or reseller, or visit the IBM worldwide contacts page