In the past I had already several blog entries related to z/VSE Multi-Version Measurement (MVM). You may use the tag "MVM" to search for these entries. Today I want to summarize some information about MVM, because I belief it's a good thing for z/VSE customers.
MVM was announced in February.
First a few links:
Now some facts:
- MVM replaces the Migration Pricing Option (MPO).
- The latest SCRT release, available since April 10, is required for MVM. SCRT data collected in April and submitted May 2 - 9 is the basis for the June 1 billing.
- 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.
- Customers using zELC, AEWLC and MWLC pricing are eligible for MVM.
- The following VSE Versions are eligible for MVM: VSE/ESA V1, VSE/ESA V2, z/VSE 3.1, z/VSE V4, z/VSE V5, z/VSE V6. They can be used in any combination.
- You may run different versions simultaneously for an unlimited duration during a program version upgrade. You can combine unsupported releases and request MVM.
- If there are any non-sub-capacity z/VSE versions running on a machine, you will be billed at the highest version price as full capacity. E.g. if you combine versions prior to z/VSE V4, the customer has to pay for full capacity.
- MVM is only possible for versions within the same machine. Multiple machines can not be combined.
- Do you need to request MVM ? It depends: sub-capacity (SCRT) customers and full capacity customers using SVC (Single Version Charging) do not need to request MVM. Any other customer paying e.g. for 2 versions need to request MVM.