IBM MQ release types

When ordering IBM MQ for z/OS 9.2, two separate features are offered on ShopZ. The features correspond to the LTS release and the CD release.

Both features are applicable to the same product ID (PID). It is the product ID that is licensed, so where one feature is licensed, there is entitlement to use the alternative feature if required.

When ordering the following IBM MQ for z/OS products, select the feature corresponding with either the LTS release or CD release.

If you are selecting products for inclusion in a ServerPac, it is not possible to choose both the LTS release and CD release in the same ServerPac order, because the products cannot be installed by SMP/E in the same target zone.

The LTS and CD releases are provided in separate sets of FMIDs. Note that these FMIDs cannot be installed in the same SMP/E target zone.

As the releases use different FMIDs, it is not possible to update a CD release with maintenance for an LTS release or the other way round. Similarly, there is no way to switch a version of the product code from LTS release to CD release or the other way round.

However it is possible to switch a queue manager between the release models, for further information see Migration

The LTS release is serviced by the application of PTFs which provide defect fixes, and cumulative security updates (CSUs), which provide security patches. Note that the PTFs resolve specific issues, and are not cumulative.

IBM provides groups of fixes in RSU levels for an LTS release.

The CD release is serviced by the application of PTFs which deliver both defect fixes and functional enhancements.

Each set of PTFs is cumulative and increases the modification level of the CD release. That is, a set of PTFs update the product and change the reported v.r.m from 9.0.1 to 9.0.2. The subsequent set of PTFs supersedes the first set, and updates the installed product to 9.0.3.

The IBM MQ 9.0.x and IBM MQ 9.1.x CD releases had separate version and release dependent FMIDs. This meant, moving from 9.0.x CD to 9.1.x CD required at least one complete SMP/E install.

From IBM MQ for z/OS 9.2.0, the CD release uses a set of FMIDs that will remain the same for all IBM MQ for z/OS releases with a version number of 9, that is, 9.2.0, 9.2.x, 9.3.0, 9.3.x and so on. This means that it is possible to continuously upgrade CD releases just by application of PTFs. For example, it is possible to go from IBM MQ 9.2.0 CD, to IBM MQ 9.2.2 CD, to IBM MQ 9.2.4 CD, to IBM MQ 9.3.0 CD, to IBM MQ 9.3.2 CD just by applying PTFs.

There are constraints and limitations, but generally a single queue manager can be migrated from using LTS release code to CD release code or from using CD release code to LTS release code provided that the target release is higher than that in use prior to the migration.

From IBM MQ for z/OS 9.2.0, it is possible to migrate back and forth between CD and LTS releases with the same V.R.M as many times as needed, and without impact on the ability to backwards migrate. For example, a queue manager can be started up at IBM MQ for z/OS 9.2.0 LTS, shut down and started up at IBM MQ for z/OS 9.2.0 CD, shut down and started up at IBM MQ for z/OS 9.2.0 LTS, and the other way round.

IBM MQ for z/OS has traditionally provided a fallback capability (backward migration) so that after a period of running following a migration, it is possible to fallback to the prior release.

This capability is retained for LTS releases, and those CD releases with a modifier of 0 such as 9.2.0 CD, but is not possible when the source or target of a migration is a CD release with a non-zero modifier number, for example, 9.1.5 or 9.2.1.

The following are valid migration scenarios, and illustrate how this principle works:

Source release	Destination release	Notes
8.0.0 LTS	9.2.0 LTS or 9.2.0 CD	Backwards migration not supported as 8.0.0 LTS is out of standard support.
9.0.0 LTS	9.2.0 LTS or 9.2.0 CD	Backwards migration supported.
9.1.0 LTS	9.2.0 LTS or 9.2.0 CD	Backwards migration supported.
9.1.5 CD	9.2.0 LTS or 9.2.0 CD	Backwards migration not supported as source release is CD with a non-zero modifier.
9.2.0 LTS or 9.2.0 CD	9.2.1 CD	Backwards migration not supported as destination release is CD with a non-zero modifier. Write to operator with reply CSQY041D is issued to confirm migration.

Within Passport Advantage® there are two separate eAssemblies for IBM MQ 9.2. One contains installation images for IBM MQ 9.2.0 Long Term Support release, and the other contains installation images for IBM MQ 9.2.x Continuous Delivery release.

Download installation images from the eAssembly according to your choice of release.

Alternatively, for the LTS release only, a media pack is available, containing product installation DVDs.

All IBM MQ versions, and for IBM MQ 9.2 both the LTS releases and CD releases, belong to the same Product Id.

Entitlement to use IBM MQ extends across the entire product (PID) subject to the constraints of licensed components and pricing metrics. This means that you can freely choose between LTS release and CD release installation images for IBM MQ 9.2.

Once an installation image has been downloaded from Passport Advantage, you should only select for installation the components for which you have purchased entitlement. See IBM MQ license information for further information about which installable components are included for each chargeable component.

It is possible to install IBM MQ 9.2.0 LTS release and IBM MQ 9.2.x CD release on the same operating system image.

If you do this, the components appear as separate installations, as supported by IBM MQ multi-version support. Each version has distinct sets of queue managers associated with that version.

Each new CD release is provided as an installation image. The new CD release can be installed along side an existing release, or, an earlier CD release can be updated in place by the installer to the new release.

The LTS release is serviced by the application of fix packs, which provide defect fixes, and cumulative security updates (CSUs), which provide security patches. The fix packs are made available periodically and are cumulative.

The only maintenance provided for a CD release will be in the form of an iFix delivered to resolve a specific customer issue, if required, on the two latest CD releases, which could be on a subsequent version.

There are constraints and limitations but, generally, a single queue manager can be migrated from using LTS release code to CD release code, or from using CD release code to LTS release code, provided that the target release is higher than that in use prior to the migration.

Once a queue manager starts running a CD release of code, the queue manager command level is updated to indicate the new release level. This means any new functions provided in the release are enabled, and it will no longer be possible to restart the queue manager using a code release with a lower v.r.m number.