The version naming scheme for IBM MQ for Multiplatforms

On Multiplatforms, IBM® MQ uses a four-digit Version, Release, Modification, and Fix (VRMF) version identifier format.

The VRMF acronym stands for:


Version.Release.Modification.Fix

Versions and releases of IBM MQ are known by the first two digits of the VRMF. The two digits are sometimes prefixed by a V, such as V9.0. A version of IBM MQ always has a release level, even if it is the first release in a version. A new version or release has a new service end date. To run a queue manager at a different VR level, you must migrate the queue manager, its applications, and the environment in which it runs.

The third digit in the VRMF identifies the modification level of a release. A change in the third digit does not change the release. For example, after upgrading IBM MQ to modification level 9.0.1, the release of IBM MQ remains 9.0. However the command level does change to 901. New modification levels generally do not result in a new service end date, but if a modification level is announced then a new service end date might be announced too.

From 1Q 2023, there are two types of maintenance:

Fix packs: Fix packs contain roll-ups of all defects fixed since the previous fix pack delivery (or GA). Fix packs are produced exclusively for Long Term Support (LTS) releases during their normal support lifecycle.
Cumulative security updates (CSUs): CSUs are smaller updates and contain security patches released since the previous maintenance (GA). CSUs are produced for LTS releases (including releases in extended support), and for the latest IBM MQ Continuous Delivery (CD) release, as required to deliver relevant security patches.

Therefore, for maintenance releases in or after 1Q 2023, the fourth digit in the VRMF represents either a fix pack number of a CSU number. Both types of maintenance are mutually cumulative (that is, they contain everything included in older CSUs and fix packs), and both are installed using the same mechanisms for applying maintenance. Both types of maintenance update the F-digit of the VRMF to a higher number than any previous maintenance: fix packs use “F” values divisible by 5, CSUs use “F” values not divisible by 5.

For maintenance releases before 1Q 2023, the fourth digit in the VRMF always represents the fix pack level. For example, the first fix pack of the IBM MQ 9.2.0 LTS release is numbered 9.2.0.1.

Maintenance levels do not affect the command level of the queue manager. No migration is required, and maintenance levels do not affect the service end date of a release.

Version naming for Long Term Support and Continuous Delivery

[Long Term Support] For Long Term Support (LTS) releases, the number consists of a four digit VRMF, for example 9.2.0.2. The F-digit is either a fix pack number, which is a value divisible by 5, or CSU number, which is a value not divisible by 5.

[Continuous Delivery] For Continuous Delivery (CD) releases, the number consists of a three digit VRM. Where a fourth digit is added to the code, it is either a zero or the F-digit of a CSU number, that is a value not divisible by 5..

In general, the two release types are distinguishable by the modification number:

Long Term Support releases always have a modification number of zero, for example 9.1.0 and 9.2.0.
Continuous Delivery releases generally have a modification number that is non-zero, for example, 9.1.4, 9.1.5, and so on.

You can find the full version level of an IBM MQ installation by typing the command dspmqver, or DSPMQMVER on IBM i. The command returns the full three-digit VRM, or four-digit VRMF.

Applying updates

Maintenance deliveries for a particular version/release are cumulative, from the initial release. You can apply any higher numbered fix pack or CSU of the same version/release to upgrade directly to that version level. You do not have to apply the intervening fixes.

You can also refresh the full version of IBM MQ by installing a manufacturing refresh that is available online or on physical media. The result of installing a manufacturing refresh is almost the same as applying a maintenance delivery to an earlier fix level of IBM MQ. However there is one important difference: Fix packs and CSUs are applied using a maintenance procedure, manufacturing refreshes are installed using an installation procedure. You can "unapply" a fix pack or CSU to return to the previous fix level you had installed. You can only uninstall a manufacturing refresh, which removes IBM MQ from your system.

In addition to manufacturing refreshes and maintenance deliveries, you might occasionally be directed by the IBM Support team to apply an interim fix. Interim fixes are also known as emergency or test fixes, and are used to apply urgent updates that cannot wait for the next maintenance delivery. Interim fixes are known by a unique fix name, which will include the target version and platform, and other identifying context, such as a support case reference or APAR number. When you apply a new cumulative security update, fix pack or manufacturing refresh, all interim fixes are removed. The documentation with maintenance delivery or manufacturing refresh includes a “fix list” page, stating which APAR fixes are included in the deliverable. This list tells you if the APARs associated with the interim fixes that you have applied have been fixed in the latest maintenance. If they have not, check to see if there are new interim fixes, at the new level, for the APARs that concern you. If there are not, consult IBM Support. They might either tell you to reapply the interim fix, or supply a new interim fix.

You get manufacturing refreshes, maintenance deliveries and interim fixes through Passport Advantage® and Fix Central. See Where to find downloadable installation images.

Manufacturing refreshes are available through Passport Advantage.
Fix packs and CSUs are available through Fix Central.
Interim fixes are typically provided directly by the IBM Support team through a support case, and may on occasion be provided through Fix Central.