IBM MQ release types and versioning

There are two main types of release for IBM® MQ; Long Term Support (LTS) and Continuous Delivery (CD). Some versions of the IBM MQ Advanced Container are IBM Cloud Pak® for Integration - Support Cycle 2 (formerly Long Term Support) (CP4I-SC2) releases.

LTS and CD release types

The aim of the two main release types is to meet the requirement for delivery of new and enhanced IBM MQ functions as rapidly as possible in the next CD release, while at the same time maintaining a stable LTS release for systems that need a long term deployment of IBM MQ, and for customers who prefer this traditional option.

The two release types are distinguishable by the modification number, that is the M digit of the VRMF:

Long Term Support releases always have a modification number of zero. For example 9.3.0 and 9.4.0.
Continuous Delivery releases usually have a modification number that is non-zero. For example 9.4.1, 9.4.2, and so on.

For each new version of IBM MQ there is an initial CD release available at the same time as the initial LTS release. Both releases have the same Modification level of zero, and both are functionally identical. For example, IBM MQ 9.4.0 is the follow-on LTS release to IBM MQ 9.3.0. It is also the follow-on CD release to IBM MQ 9.3.5.

Each LTS release is supported for the duration of the release. Each CD release is supported for 12 months or while it is one of the most recent two CD releases, whichever is longer.

Note: IBM MQ Explorer, IBM MQ Operator and IBM MQ Container releases are CD only. See Version support for the IBM MQ Operator.

For more information, see IBM MQ FAQ for Long Term Support and Continuous Delivery releases.

To check the IBM MQ version:

Type the command dspmqver, or DSPMQMVER on IBM i. The returned messages include the three-digit VRM or, if maintenance has been applied, the four-digit VRMF.
Use the REST API GET method.
View the queue manager property panel in IBM MQ Explorer.
Look at the CSQY000I message in the queue manager job log. This message is issued when the queue manager starts, and shows the release level and release type.

The command level of a queue manager is the three-digit VRM level. An IBM MQ program can call MQINQ, passing the MQIA_COMMAND_LEVEL selector, to get the command level of the queue manager it is connected to. You can also view the queue manager command level in the queue manager property panel in IBM MQ Explorer.

Maintenance delivery model

There are two types of maintenance release, fix packs for LTS releases and Cumulative Security Updates (CSUs) for LTS and CD releases:

Fix packs provide the latest security and functional fixes.
CSUs provide the latest security fixes.

Both types of maintenance are mutually cumulative (that is, they contain all fixes included in older CSUs and fix packs) and both are installed using the same mechanisms for applying maintenance. So 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.

Both types of maintenance update the F digit of the VRMF to a higher number than any previous maintenance:

For LTS releases, the F digit of the VRMF is either a fix pack number, which is a value divisible by 5, or a CSU number, which is a value not divisible by 5. For example, 9.3.0.5 is a fix pack and 9.4.0.1 is an LTS CSU.
For CD releases, the F digit of the VRMF is either a zero or a CSU number, which is a value not divisible by 5. For example, 9.3.2.1 is a CD CSU.

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.

For more information, see Changes to IBM MQ's maintenance delivery model.

For each supported platform, the release type you choose affects ordering, installation, maintenance and migration. For more information, see IBM MQ release types: planning considerations.

Maintenance delivery model: differences by platform

For Multiplatforms, LTS fix packs and CSUs, and CD CSUs,

are downloaded as interim fixes
are downloaded by fix pack or CSU number
are cumulative

[MQ 9.4.0 Jun 2024] From IBM MQ 9.4, on Windows and Linux® platforms both types of maintenance are full install images that can be used for a new installation or upgrading an existing installation. On AIX® and IBM i the CSU and fix pack maintenance process is unchanged and requires a base install image to apply to.

For z/OS®, LTS fix packs and CSUs

are downloaded as interim fixes
are downloaded by Program Temporary Fix (PTF) number
are cumulative

z/OS CD CSUs are not usually made available as separate downloads. They are bundled into the next CD release. If you cannot wait for the next CD release, you can request a CD CSU as a USERMOD.

IBM MQ Advanced Container and the CP4I-LTS release model

[MQ 9.4.1 Oct 2024] From IBM MQ Advanced 9.4.1, the prebuilt IBM MQ Advanced Container is supported standalone. The prebuilt IBM MQ Advanced Container for version 9.4.0 is only supported when deployed using the IBM MQ Operator on the Red Hat® OpenShift® Container Platform. IBM MQ Operators are supported for use as part of the IBM Cloud Pak for Integration, or independently. The IBM Cloud Pak for Integration uses the IBM Cloud Pak for Integration - Support Cycle 2 (formerly Long Term Support) (CP4I-SC2) release model. This provides support for up to 2 years, with an optional extension for another year, for each CP4I-LTS release.

The IBM MQ Advanced Container image is based on IBM MQ Continuous Delivery, and is typically supported as a CD release. However, if a container image is based on a version of IBM MQ 9.4, and the container is used as part of the IBM Cloud Pak for Integration, the container is instead supported as a CP4I-LTS release.

For detailed mappings between IBM MQ Operators, IBM Cloud Pak for Integration versions, and container images, see Release history for IBM MQ Operator.