Product Documentation
Abstract
This FAQ is applicable to IBM MQ 9.0 and later releases. Starting with IBM MQ 9.0, IBM MQ introduced the support model described below.
Content
*IBM MQ Appliance firmware LTS duration is 3 years from general availability.
*IBM MQ software products LTS duration is 5 years from general availability.
IBM MQ is released as a Continuous Delivery (CD) offering with regular update packages. Each update incrementally delivers new capability and defect fixes. Long Term Support (LTS) packages just receive security and defect fixes through fix packs and individual fixes with no incremental functional enhancements.
- For IBM MQ, defect fixes for a CD update may be requested if it is one of the most recent two CD updates, or within 12 months of General Availability, whichever is longer.
- A CD update package may be declared an LTS release, which is supported for a minimum of 5 years for IBM MQ software and 3 years for IBM MQ Appliance firmware.
- If a CD update is no longer eligible for defect fixes, update to a package that is eligible, and if the defect can be recreated a fix will be provided.
For supported operating systems and other system requirements on both the CD and LTS releases see the IBM MQ system requirements page .
For information on available LTS and CD releases and latest fixes, see the IBM MQ fixes by version page .
Jump to MQ Appliance specific questions
Jump to MQ Operator / Container specific questions
Q. What do you mean by LTS and CD releases?
A. LTS stands for Long Term Support. This corresponds with the way we supported and maintained MQ in releases earlier than 9.0. The Long Term Support release is for systems which demand the highest levels of stability - updates during the support period contain fixes to identified problems and vulnerabilities. CD stands for Continuous Delivery. The CD releases add new function to MQ on a regular cadence and are intended for customers wanting to exploit the latest features and capabilities of MQ without waiting for the next long term support release cycle. Fixes are only provided on the LTS and two most recent CD Releases.
Q. What's the frequency of LTS and CD releases?
A. The exact duration between releases is not fixed but the expected frequency is LTS releases approximately every two years and CD releases every few months.
Q. How are LTS releases numbered?
A. Using the V.R.M.F format described here a newly released LTS release is in the format X.Y.0.0, where either X or Y has been increased since the previous LTS release and the modification number and fix level are zero. Subsequent fix packs or security maintenance deliveries will increase the fix level (see "How are maintenance deliveries numbered?" below). MQ for z/OS is similar, but uses a three digit V.R.M format, and doesn't have fixpacks.
Q. How are CD releases numbered?
A. Using the V.R.M.F format described here a newly released CD releases is in the format X.Y.Z.0, where X and Y match that of the most recent LTS release, and Z (the modification number) indicates the CD delivery since the matching LTS release was delivered. The final .0 may be omitted for the GA level in some cases. If security maintenance is made available for a CD release, the fix level is increased, for example to X.Y.Z.1.
From 9.2 onwards there will be an MQ for z/OS CD release available at the same time as the corresponding LTS release, and they will have the same V.R.M number. For example, there is both an IBM MQ for z/OS 9.2.0 LTS release and an IBM MQ for z/OS 9.2.0 CD release.
Q. How are maintenance deliveries numbered?
From the start of 2023, there are 2 types of maintenance delivery for LTS releases. Both will increment the fix level of the V.R.M.F version identifier. Fix packs, containing a roll-up of fixes will increment the fix level to the next multiple of 5 - for example 9.3.0.10 or 9.3.0.15. Cumulative security update (CSU) maintenance will increment the fix level to the next number that is not a multiple of 5, for example 9.3.0.11 or 9.3.0.12. Both types of maintenance are delivered and applied in the same manner.
From the start of 2023, the latest CD release will also receive CSU maintenance when required. These will increment the fix level to the next number that is not a multiple of 5, for example 9.3.1.1 or 9.3.1.2. CD releases do not receive fix pack maintenance.
For more information on the difference between CSU and fix pack maintenance, and how maintenance applies to CD and LTS releases, refer to the description of changes to IBM MQ's maintenance delivery model.
Q. Do I need a different license to install LTS or CD releases?
A. No. Both types of release are covered by the same license.
Q. Where do I obtain an LTS or CD installation?
A. LTS and CD are installed from separate installation binaries. Both types are available through Passport Advantage or ShopZ. For ShopZ make sure you download the correct orderable feature (LTS or CD) to match the future upgrade path you wish to follow.
Q. What happens with the IBM MQ on IBM Cloud service?
A. The IBM MQ on IBM Cloud managed service is using the continuous delivery releases. Each time a new release is made available the service will give a 30 day window for the update to be completed.
A.
- For IBM MQ software products a LTS release is supported for at least five years from the point that it is made generally available.
- For IBM MQ Appliance a LTS release is supported for three years from the point that it is made generally available
Q. What is the support model for a CD release?
A. Support of a CD release is based on the support lifetime of the related LTS release. So support for CD release X.0.3 is provided while X.0.0.0 is in support. For urgent resolution of problems, an iFix or APAR fix can be provided for a CD release for 12 months from the availability of the release or while it remains one of the two most recent CD releases, whichever is longer.
Q. How do I raise a problem with an LTS or CD release?
A. There is no change to how problems are raised for IBM MQ in this model. As before any problems requiring IBM investigation should have a Case raised through the IBM support portal.
Q. How are fixes delivered for a LTS release?
A. As previously, if a fix is required for a LTS release, where possible, IBM provides an iFix or APAR fix for the level of LTS installed on your system. While an LTS release is in support, identified fixes are shipped as PTFs for z/OS or rolled up into fix packs on distributed platforms and made available at regular intervals. Users of the IBM MQ Appliance should see the Appliance-specific question below.
Q. How are fixes delivered for a CD release?
A. If a fix is required for a CD release we aim to deliver it in the next CD or LTS release. For urgent resolution of problems, an iFix or APAR fix can be provided for a CD release for 12 months* from the availability of the release or while it remains one of the two most recent CD releases, whichever is longer. A new CD release contains fixes identified since the previous CD release. Much like a fix pack. Users of the IBM MQ Appliance should see the Appliance-specific questions below.
A. IBM MQ Appliance firmware interim fixes are always provided on the latest available fixpack level of your chosen LTS release. Interim firmware fixes cannot be produced on back-level fix packs.
Q. How are interim fixes for CD firmware releases on the MQ Appliance handled differently?
A. IBM MQ Appliance firmware interim fixes are provided on the latest available CD release. When it is less than 6 months since the release of the previous CD firmware, on request IBM will assess the feasibility of making reasonable efforts to provide an interim fix on the previous CD firmware level, however IBM cannot guarantee that all fixes can be retrofitted into earlier code.
A. An IBM MQ LTS Operator and container image is only available via Cloud Pak for Integration entitlement. With IBM MQ entitlement the Operator and container images are only available as CD updates with no LTS. The reason for this is that the MQ LTS duration is min 5 years, which is much longer than underlying dependencies such as OpenShift are supported for.
Q. Does that mean the last CD release before an LTS release also gets fixed?
A. The "two most recent CD releases" applies across new LTS releases. For example, if a problem is identified running on W.0.4 but a new LTS release W.1.0.0 has been delivered with subsequent CD releases W.1.1 and W.1.2, fixes can only be provided for those most recent CD releases.
Q. Can I install both LTS and CD based systems on the same OS image?
A. Yes.
Q. Can channels from LTS based systems connect with CD based systems?
A. Yes, All MQ queue managers interoperate with queue managers running at a different version, whether they're using an LTS or CD release.
Q. On z/OS, can LTS and CD based systems access the same shared queues?
A. Generally yes. From time to time we might introduce new function in an LTS or CD release which has specific restrictions.
Q. Can a MQ cluster contain both LTS and CD queue managers?
A. Yes, queue managers of different levels can interoperate in an MQ cluster. However, it might not be possible to use newer cluster capabilities only available in the version of some of the queue managers.
Q. Can an MQ cluster's full repository queue managers be from an LTS release and other queue managers at new CD releases?
A. Yes. However, if the CD queue managers intend to exploit new clustering capabilities, the full repository queue managers might also need to be upgraded. This will be a documented requirement of the feature.
Q. What features do you see in a CD release?
A. New features are delivered in each CD release. By the nature of the regular delivery, large features might be delivered across multiple CD releases, increasing the extent of the feature each time.
Q. Will new features be exactly the same from one CD release to another?
A. Potentially not. CD releases provide new capabilities as rapidly as possible, which might mean that a feature delivered in one CD release is improved in a subsequent CD release, based on further development or user feedback. This might change the external administration and behavior of a new feature. For this reason, some migration work might be required when new CD features are enabled.
Q. How do I identify if a feature is liable to change under subsequent CD releases?
A. The documentation of the feature indicates if this feature is currently only available through CD releases and therefore liable to change.
Q. Can I prevent new CD features being available on a queue manager?
A. No. All new CD features are enabled on a queue manager. Depending on the nature of the new feature it might be possible to disable it through configuration or just not use the feature, but new features are enabled and available for use by default.
Q. How does the command level (CMDLEVEL) of a queue manager change with a CD or LTS release?
A. The CMDLEVEL is automatically set to a command level that matches the installed CD or LTS release. The user cannot reduce or hold back the command level. The command level does not change between fix packs of an LTS release, for example between 9.0.0.0 and 9.0.0.4.
Q. Where do I find documentation for the LTS and CD releases?
A. Documentation for LTS and CD releases are in the same section of IBM Knowledge Center. For example, documentation for 9.0.0.x LTS and 9.0.x CD releases are in the IBM MQ Version 9.0 section, and documentation for 9.1.0.x LTS and 9.1.x CD releases are in the IBM MQ Version 9.1 section. CD and LTS content are both identified by a blue rectangular icon containing a version number.
For LTS content, the icon is dark blue and contains the LTS release and Fix Pack number. For example 
For CD content, the icon is light blue and contains the CD release number. For example 
Q. Are all the new features in a CD release supported?
A. Yes, if you choose to use any new feature, support is provided through the standard methods. If any fix is required it is delivered as previously described.
Q. What features do you see in an LTS release?
A. When a new LTS is released it contains versions of the features introduced in the CD releases produced on top of the previous LTS release. Occasionally, features introduced in a CD release just prior to a new LTS release might not be included in the LTS release, or might be included in a modified form.
Q. Do new features change from one LTS release to another?
A. No. After features are delivered in an LTS release every effort is made to maintain the external administration and behavior of the features available, in the same way as has been done in the past.
Q. Can I migrate a queue manager from an LTS release to a CD release?
A. You can migrate from an LTS release to a CD release at the same or higher version or release number. For example from X.0.0.4 to X.0.3
Q. For z/OS, will you provide backward migration capability after migrating from an LTS to a CD release?
A. In general, no, and this will be indicated by message CSQY040I in the queue manager’s logs. Prior to moving to a CD release consider taking a backup of the LTS installation that could be restored.
However backwards migration is supported if you have migrated from an LTS release to a CD release with a modification number of 0. For example, if you migrate from 9.1.0 LTS to 9.2.0 CD then backwards migration to 9.1.0 LTS is supported. Message CSQY039I will be displayed in the queue manager’s logs if backwards migration is supported.
Q. For distributed platforms, will you provide backward migration capability after migrating from an LTS to a CD release?
A. No. Once queue manager data and objects have been migrated to the new CD release it is not possible to go backwards. Prior to moving to a CD Release consider taking a backup of the LTS installation that could be restored.
Q. On z/OS can I install PTFs to upgrade from one CD release to a second CD release where the second CD release is across an LTS release boundary?
A. No. You cannot upgrade across an LTS release boundary by installing PTFs. For example you can't upgrade from 9.0.5 to 9.1.1 using PTFs. A new CD product (hence FMID) matching the most recent LTS release needs to be ordered and installed. You can however migrate queue managers across LTS boundaries, for example from 9.0.5 to 9.1.1.
Q. On z/OS can I install PTFs to upgrade from one CD release to a subsequent LTS release?
A. No. You cannot upgrade from a CD release to an LTS release by installing PTFs. For example you can't upgrade from 9.0.5 to 9.1.0 using PTFs. A new LTS product (hence FMID) needs to be ordered and installed. You can however migrate queue managers from a CD release to a subsequent LTS release, for example from 9.0.5 to 9.1.0.
Q. What are the differences between MQ for z/OS CD and LTS releases that have the same V.R.M number, for example 9.2.0 CD and 9.2.0 LTS?
A. From a functional perspective there is no real difference between the two releases. The main difference is the way that the two releases are serviced, as described above, and the fact that the releases are installed using different FMIDs. As previously mentioned, it is possible to migrate queue managers between CD and LTS releases with the same V.R.M number, and 9.2.0 CD supports backwards migration even though it is a CD release.
Q. Can I migrate a queue manager from a CD release to an LTS release?
A. You can migrate from a CD release to an LTS release at a higher version or release number. For example from X.0.3 to X.1.0.0. From MQ for z/OS V9.2 it is possible to have both a CD and LTS release with the same V.R.M number, for example 9.2.0, in this case it is also possible to migrate a queue manager between the two releases.
Q. For z/OS, do you provide backward migration capability after migrating from a CD to an LTS release?
A. In general, no, and this will be indicated by message CSQY040I in the queue manager’s logs. However, from MQ for z/OS V9.2 it is possible to have both a CD and LTS release with the same V.R.M number, for example 9.2.0. In this case it is possible to migrate a queue manager between the two releases as they are functionally identical.
Q. Can I migrate a queue manager from one CD release to another CD release?
A. You can migrate from a CD release to another CD release at a higher version, release or modification number. For example from X.0.3 to X.0.5
Q. To migrate a queue manager do I have to move up through every CD or LTS release?
A. No. Migration is possible from any in support LTS or CD release to a later LTS or CD release.
Q. Will a queue manager previously running under one CD release run under a new CD release?
A. Yes. The queue manager can be migrated from one CD release to another along with its data. However, as already described, features provided under the earlier CD release might have been modified in the later release and some modification to the configuration or applications using the new features might be required.
Q. Will a queue manager previously running under one LTS release run under a new CD release?
A. Yes. The queue manager can be migrated from one CD release to another along with its data.
Q. Will a queue manager previously running under one CD release run under a new LTS release?
A. Yes. The queue manager can be migrated from one CD release to a later LTS release along with its data. However, as already described, features provided under the earlier CD release might have been modified in the later release and some modification to the configuration or applications using the new features might be required.
Q. Can I roll back a CD install to an earlier CD release or LTS release?
A. No. It is not possible to rollback any CD install.
Q. Can I roll back an LTS release to an earlier CD release?
A. No. It is not possible to rollback to a CD install.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
22 November 2023
UID
swg27047919