Multi-Version Measurement (MVM)

Multi-Version Measurement (MVM) for z/OS and z/VSE removes time limits for running multiple eligible versions of a software program. Clients may run different versions of a program simultaneously for an unlimited duration during a program version upgrade. Clients may also choose to run multiple different versions of a program simultaneously for an unlimited duration in a production environment. MVM allows clients to selectively deploy new software versions, providing more flexible control over their program upgrade cycles.

Originally introduced as "Multiplex Version Measurement" for Country Multiplex Pricing clients, this price offering has been renamed to "Multi-Version Measurement" and extended to all z/OS and z/VSE clients during 2017. MVM replaces Single Version Charging (SVC), the Migration Pricing Option (MPO), and the IPLA Migration Grace Period.

MVM replaces Single Version Charging (SVC)

MVM implementation differs depending upon the client’s configuration (Full Capacity versus Sub-Capacity) and depending upon the price metric for any specific software license within a Program Family. A Program Family is the set of all the Program IDs for a software program having multiple MVM-eligible versions.

The tables in the z Systems Software Contracts Exhibits website show the program versions and Program IDs that correspond to a given Program Family for MLC programs and IPLA programs. Program Family definitions are updated as new versions are announced.

MVM for Sub-Capacity programs

All sub-capacity machines that run multiple versions of a sub-capacity-eligible program under MVM will be measured and priced according to MVM terms. For clients running multiple versions of a sub-capacity program, such as DB2 for z/OS, all MSUs for the multiple versions of DB2 within that Program Family will be reported on a concurrent basis, similar to how SCRT has reported z/OS since z/OS V2 since it became available.

SCRT will calculate the combined concurrent peak (indicated by "(All)" in the report) by adding up the LPAR values where any version of the program is running. 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 versions and releases of a program, such as DB2, reported as though it was a single version.

Reporting and charging for Sub-Capacity programs under MVM

When only one program version in a Program Family is reported by SCRT, the sub-capacity value reported for that program version will only be charged against the latest Program Family version licensed on that machine. The latest program version licensed may not be the program version that is listed on the SCRT report.

When two or more program versions in a Program Family are reported by SCRT, the sub-capacity (All) MSU value reported for that Program Family will only be charged against the latest Program Family version licensed on that machine. This applies whether or not one of the program versions is discontinued during or after the SCRT Reporting Period. The reported (All) MSUs will be charged against the latest program version licensed on that machine on the billing effective date. Only if all the program versions within a Program Family are discontinued will no billing occur.

When no version of an MLC licensed program is reported by SCRT, the product minimum MSUs will be charged against the latest Program Family version licensed on that machine, as per standard sub-cap terms.

Initial month charging under MVM when a new MLC Program Family is ordered

This section only applies to the initial month charging period, and only when a completely new MLC middleware program is being added. For example, a customer without MQ for z/OS acquires MQ for z/OS for the first time.

Under existing MLC sub-capacity terms, the first month is charged at the capacity of the Operating System MSUs. There is no change to this rule when only one version of an Operating System is present.

Under MVM, if multiple versions of an Operating System are present, such as z/OS V1 and z/OS V2, the initial month billing MSUs are the reported (All) MSUs for that Operating System. This is the same as under the prior MPO rules.

Under MVM, if multiple price metrics for an Operating System are present, such as AWLC and zNALC for z/OS, the initial month billing MSUs are the reported overall z/OS (All) MSUs. This is the same as under the prior MPO rules.

MVM for programs not eligible for Sub-Capacity

When all the program versions within a Program Family are charged under Full Capacity MSUs the latest licensed version of the program is charged at the Full Capacity MSUs of the machine and charges for any earlier versions of the program in that family are waived.

When all program versions within a Program Family are charged with a price metric which is not MSU‑based (e.g. zELC), or otherwise ineligible for Sub-Capacity, the latest licensed version of the program is charged using the applicable metric and charges for any earlier versions in that Program Family are waived.

MVM replaces the Migration Pricing Option (MPO)

Updates to MPO rules for Operating Systems: MVM will now apply to both the z/OS and z/VSE Operating Systems, replacing the MPO. The Operating System (All) MSUs as currently reported by SCRT have not changed; the only difference from MPO is that there is no longer a 24-month (z/OS) or 18-month (z/VSE) time limit. Clients may now choose to run multiple versions of z/OS or z/VSE without the prior MPO time limit restrictions.

Updates to MPO rules for z/VSE middleware: MVM will now apply to clients migrating to CICS TS for z/VSE V2 and IBM TCP/IP for z/VSE V2, replacing the MPO. The (All) MSUs as reported by SCRT have not changed; the only difference from MPO is that there is no longer an 18-month time limit. Clients may now choose to run multiple versions of CICS TS for z/VSE and IBM TCP/IP for z/VSE without the prior MPO time limit restrictions.

MVM replaces the IPLA Migration Grace Period

Migration of IPLA program versions: The previously announced Migration Grace Period time limit of six months for IPLA program version migrations will be eliminated under MVM. 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, MVM 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. MVM does not extend support dates for programs withdrawn from service.

  • Execution-based: For sub-capacity IPLA Execution-based programs, the peak MSUs used for billing purposes will be the concurrent MSU peak reported by SCRT for that Program Family. For clients running multiple versions of a given program, SCRT will report an (All) MSUs row that shows the concurrent peak for all versions of the program running on the machine.
  • Reference-based: For sub-capacity IPLA Reference-based programs, the peak MSUs used for billing purposes will be the concurrent MSU peak reported by SCRT for the associated Parent Program family. For clients running multiple versions of a given Parent Program, SCRT will report an (All) MSUs row that shows the concurrent peak for all versions of the Parent Program running on the machine.
  • z/OS-based: For sub-capacity IPLA z/OS-based programs, the peak MSUs used for billing purposes will be the concurrent MSU peak reported by SCRT for z/OS. For clients running multiple versions of z/OS, SCRT will report an overall z/OS row that shows the concurrent peak for all versions of z/OS running on the machine, including when both z/OS Traditional and z/OS zNALC are present.

MVM and Country Multiplex Pricing (CMP)

CMP terms and conditions are unchanged by the MVM announcement. The Multiplex Version Measurement offering originally announced as part of Country Multiplex Pricing is now renamed as Multi-Version Measurement for consistency with non-CMP offerings.

Transitioning from SVC and MPO to MVM

Full Capacity clients with SVC or MPO in effect through May 31, 2017 (or after) will be converted to MVM terms on June 1, 2017. Clients being charged for multiple versions of eligible Full Capacity programs whose SVC or MPO period expired prior to the availability of MVM must request in writing to IBM that MVM be applied to those eligible programs.

Sub-capacity licenses cannot be charged under MVM terms until an SCRT V24.2.0 or SCRT V24.11.0 (or later) sub-capacity report containing a combined concurrent peak MSU value for multiple program versions in an eligible Program Family is submitted to IBM. If MVM is not implemented when an SVC or MPO expires then billing will resume for the previously-waived version.

SCRT V24.2.0 and SCRT V24.11.0 are planned to be available on April 10, 2017, therefore the first SCRT sub-capacity report capable of containing a combined concurrent peak MSU value for multiple program versions in an eligible Program Family can be generated on May 2, 2017. This report, for data collected during the April reporting period, may be submitted between May 2 and May 9, 2017, and will have a billing effective date of June 1, 2017.

Submission of an SCRT report that supports MVM will be considered a request by the client to switch from any existing pre-MVM terms to MVM terms. Clients being charged for multiple versions of Sub-Capacity programs will only be charged for the latest Program Family version after implementing MVM.

When all the licensed versions in an MLC Program Family are Sub-Capacity priced and are under SVC terms at the time of transition to MVM:

  • If multiple program versions in a Program Family are licensed and being reported then the (All) MSUs will be charged against the latest licensed version in the Program Family, and the rest of the eligible versions in the Program Family have their charges waived.
  • If multiple program versions in a Program Family are licensed but only one is being reported by SCRT then the sub-capacity value reported for that version will only be charged against the latest Program Family version licensed on that machine and all older version charges are waived.
  • If multiple versions in a Program Family are licensed but none are being reported by SCRT then the product minimum MSUs will only be charged against the latest Program Family version licensed on that machine and all older version charges are waived.

MVM News

On 14 February 2017 IBM announced Multi-Version Measurement replaces Single Version Charging for eligible z/OS and z/VSE software programs, providing z Systems clients with more flexibility for new software deployments and software upgrade cycles. MVM also replaces the Migration Pricing Option (MPO) and the IPLA Migration Grace Period.

Call us at 1-866-261-3023 | Priority code: z Systems

Visit us

Visit us