IBM MQ release types: planning considerations

From IBM® MQ 9.0 there are two types of release; a Long Term Support (LTS) release and a Continuous Delivery (CD) release. For each supported platform, the release type you choose affects ordering, installation, maintenance and migration.

For detailed information about the release types, see IBM MQ release types and versioning.

[UNIX, Linux, Windows, IBM i]

Considerations for IBM MQ for Multiplatforms

Ordering

Within Passport Advantage there are two separate eAssemblies for IBM MQ 9.1. One contains installation images for the IBM MQ 9.1.0 Long Term Support release, and the other contains installation images for the IBM MQ 9.1.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.1 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.1.

Installation

After you download an installation image from Passport Advantage, you should select for installation only 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.

You can install IBM MQ 9.1.0 LTS release and IBM MQ 9.1.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 alongside an existing release, or, an earlier CD release can be updated in place by the installer to the new release.

CD releases contain functional enhancements as well as the latest set of defect fixes and security updates. Each CD release is cumulative, and wholly replaces all prior ones for that version of IBM MQ. So you can skip a specific CD release if it does not contain any function that is relevant for your enterprise.

Maintenance

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 and CSUs are made available periodically and are cumulative.

For CD, CSUs are produced for the latest CD release only, which might be on a subsequent version.

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.

Migration between LTS release and CD release

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.

Two approaches are possible:
  • Install the new release of code in place so that an existing installation of IBM MQ is updated. Any queue managers associated with the installation use the new release of code when started.
  • Install the new release of code as a new installation, then move individual queue manager instances to the new installation using the setmqm command.

When 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 you can no longer restart the queue manager using a code release with a lower VRM number.

[z/OS]

Considerations for IBM MQ for z/OS

Ordering
When ordering IBM MQ 9.1 for z/OS®, 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, you select the feature corresponding with either the LTS release or the CD release:
  • IBM MQ for z/OS 9.1
  • Managed File Transfer for z/OS 9.1

If you are selecting products for inclusion in a ServerPac, you cannot 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.

Advanced Message Security for z/OS (AMS) 9.1 provides both the LTS release and CD release options.

The release options are selected by choosing the equivalent release for the base product, IBM MQ for z/OS 9.1, and enabling with the product 5655-AM9.

Attention: You cannot choose CD release enhancements for AMS functions on an LTS release IBM MQ base.

If your enterprise uses IBM MQ for z/OS Value Unit Edition (VUE) 9.1, the same product 5655-VU9 enables VUE licensing in either the LTS release or CD release of IBM MQ for z/OS 9.1.

Installation
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. If you need both the LTS and CD releases:
  • Install the LTS release and CD release in separate target zones
  • Maintain separate target and distribution libraries for the two releases

If your queue manger is in a queue sharing group, when you upgrade to the latest CD version you must upgrade all queue managers in the group.

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.

Because the releases use different FMIDs, you cannot 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, you can switch a queue manager between the release models. See Migration between LTS release and CD release.

You can distinguish between an LTS and CD release with the same VRM level by looking at the CSQY000I message in the queue manager job log.

Maintenance

IBM MQ for z/OS uses PTFs for Maintenance.

[Long Term Support]PTFs are specific to a particular set of libraries corresponding to specific release level. For UNIX System Services features (that is, JMS and WEB UI, Connector Pack, and Managed File Transfer) the z/OS PTFs are aligned directly with the Multiplatforms fix packs and cumulative security updates (CSUs). These fixes are cumulative, and are made available at the same time as the equivalent Multiplatforms fix pack or CSU.

[Continuous Delivery]CD CSUs are not usually made available between CD releases, but are included in the next IBM MQ for z/OS CD release. You can also contact support to request a ++USERMOD.

Other fixes on IBM MQ for z/OS are distinct fixes on particular parts. These fixes resolve specific issues, are not cumulative, and are made available as and when they are produced.

Migration between LTS release and CD release

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.

IBM MQ for z/OS has traditionally provided a fallback capability (backward migration) so that after a period of running following a migration, you can fall back to the prior release. This capability is retained for LTS releases, but is not possible when the source or target of a migration is a CD release.

The following are valid migration scenarios, and illustrate how this principle works:
[V9.1.0 Aug 2018]
Source release Destination release Notes
V8.0.0 V9.1.0 LTS Backwards migration always supported, provided backwards migration PTFs applied at V8.0.0.
V9.0.0 V9.1.0 LTS Backwards migration always supported, provided backwards migration PTFs applied at V9.0.0.
V9.0.5 CD V9.1.0 LTS No backwards migration, source release is CD.
[V9.1.1 Nov 2018] V9.0.0 [V9.1.1 Nov 2018]V9.1.1 CD [V9.1.1 Nov 2018]No backwards migration, target release is CD.

Write to operator with reply CSQY041D is issued to confirm migration.