The version naming scheme for IBM MQ for z/OS

On IBM MQ for z/OS®, releases have a three digit Version, Release, and Modification (VRM) code. To run a queue manager at a different VRM level, you must migrate the queue manager, its applications, and the environment in which it runs. Depending on the migration path, the migration might require more or less effort.

The release level of IBM MQ for z/OS is described by a three-digit VRM code. This applies to both the Long Term Support (LTS) release and the Continuous Delivery (CD) release model.

The two release types are distinguishable by the modification number in the version.release.modification (v.r.m) release identifier.

Long Term Support releases have a modification number of zero, for example, 9.0.0.

Continuous Delivery releases have a modification number that is non-zero, for example, 9.0.1, 9.0.2, and so on.

7.0.1, 7.1.0, 8.0.0, and 9.0.0 are examples of IBM MQ for z/OS release level codes.

On z/OS, a release of IBM MQ always has a three-digit VRM code, even if the release is the first release in a version, such as 8.0.0. IBM MQ for z/OS follows a convention of changing the VRM when the product is installed by SMP/E with a new FMID.

We can modify existing libraries, without changing the FMID, by applying PTFs. We cannot upgrade existing libraries to an FMID or release level by applying PTFs.

The release level of a z/OS queue manager is written to the operator console in the message CSQY000I.

The command level of a queue manager is a three-digit VRM code. We can look at the queue manager command level in the queue manager property panel in IBM MQ Explorer. An IBM MQ program can call MQINQ, passing the MQIA_COMMAND_LEVEL selector, to obtain the command level of the queue manager it is connected to.

The VRM code, or release level, is significant in two respects. Changing the release level that a queue manager runs at, requires migration of the queue manager. It also requires attention to the PTF level of other queue managers that are in the same queue sharing group. It is also significant because each release level has its own service life, and end of service date.

The service life depends on the VRM. Each release level has its own service end date. So, for example, 8.0.0, on z/OS, has a different service end date from 8.0.1. See the Software lifecycle search results for "IBM MQ". Scroll through the search results to find your version of IBM MQ, then follow the link to find the service life and end of service dates.

Note: Backward migration z/OS is possible only if you are using the Long Term Support model.