IBM MQ 9.1 LTS entered Extended Support on 30 September 2023, and under those terms its critical defect support runs out on 30 September 2026. IBM MQ 9.2 LTS entered Extended Support on 30 September 2025, with critical defect support to 30 September 2028. If you are running 9.1, the window for critical fixes closes within weeks, not years.
End of support does not switch anything off. The queue managers keep running exactly as they did. What stops is the flow of security fixes and defect corrections — which converts a working system into an audit finding.
What IBM MQ end of support actually means
Three distinct dates matter, and they are routinely collapsed into one in internal conversations:
- End of standard support. The version leaves the normal support lifecycle. No further fixes under your base entitlement.
- Extended Support. A paid IBM offering covering a defined window past that date. Critically, defect fixes are limited to the first year of the extension — after that you are buying assistance, not corrections.
- End of Extended Support. The hard stop. Nothing further is available from IBM at any price.
The distinction matters because "we're on Extended Support" is often used internally to mean "we're fine." For most of that window, you are covered for advice but not for new defect fixes.
IBM MQ lifecycle dates by version
| Version | GA | Extended Support began | Critical defect support to | Extended Support to |
|---|---|---|---|---|
| 9.1 LTS | 23 Jul 2018 | 30 Sep 2023 | 30 Sep 2026 | 30 Sep 2027 |
| 9.2 LTS | 23 Jul 2020 | 30 Sep 2025 | 30 Sep 2028 | 30 Sep 2029 |
| 9.3 LTS | 23 Jun 2022 | See IBM lifecycle page | — | — |
Why we are not publishing a 9.3 or 9.4 date here
IBM's stated policy is five years of standard support from general availability, with Extended Support purchasable for up to four more years. Applied mechanically to 9.3's 23 June 2022 GA, that arithmetic points at mid-2027 — but IBM sets announced dates per release and they do not always land where the policy formula suggests. Both 9.1 and 9.2 have Extended Support beginning on a 30 September boundary rather than their July GA anniversary, which is exactly the kind of adjustment that breaks the calculation.
So: confirm 9.3 and 9.4 against IBM's product lifecycle page before you put a number in a compliance document. A date you calculated is not a date IBM committed to, and an auditor will ask which one you are relying on.
What running past end of support actually costs
The operational risk is the obvious part: unpatched CVEs accumulate with no upstream fix coming. The part that tends to force the decision is the audit one.
In regulated environments the support status of the software is itself the finding, independent of whether anything has gone wrong. We worked with a government agency evaluating alternatives to IBM MQ support where the binding requirement was a 48-hour critical patch response commitment that the vendor contract had to explicitly state — not best-effort, not "as available." An unsupported version cannot satisfy a clause like that at any price.
The other cost is less visible. In our IBM MQ total cost of ownership work, the expensive part is rarely the license line — it is spread across support contracts, hardware, operational labour, and the risk premium attached to legacy vendor lock-in. Teams comparing an upgrade against a migration usually compare license costs and miss the other four.
Your three options, and how to choose
- Upgrade to a supported LTS release. The straightforward path if your queue manager estate is standard and you have the change window. Check application compatibility and client library versions first — clients and managed file transfer agents fall out of support on their own schedule alongside the server.
- Buy Extended Support as a bridge. Correct when you have a migration already scoped and need to stay compliant while it runs. Wrong as a standing position, because defect fixes stop after the first extended year while the bills continue.
- Migrate the workload. Worth modelling when the TCO comparison — not the license comparison — favours it. Enterprises are reasonably risk-averse here given how critical messaging infrastructure is, so the credible version of this option pairs a staged migration path with a commercial support model that matches the SLA you are giving up.
There is no universally right answer. There is a right answer for your core count, your regulatory position, and how much of the estate is genuinely IBM-MQ-specific rather than portable.
How to check where you actually stand
- Run
dspmqveron every queue manager host. Record version, release, and maintenance level. - Map each to IBM's published lifecycle dates — not to the policy formula.
- Check clients and managed file transfer agents separately; they have their own end-of-support dates and are the component teams most often forget.
- Write down which of the three options applies per environment. Production and DR frequently land differently from dev and QA.
Talk to AceMQ about your IBM MQ estate
FAQ
What does IBM MQ end of support actually mean?
It is the date IBM stops providing fixes and assistance for a version under standard support. The software keeps running — nothing switches off — but you stop receiving security fixes and defect corrections, which is what turns it into a compliance and risk problem rather than an availability one.
When does IBM MQ 9.1 go out of support?
IBM MQ 9.1 LTS reached general availability on 23 July 2018 and entered Extended Support on 30 September 2023. Under the Extended Support terms, critical defect support runs to 30 September 2026, and Extended Support itself is available until 30 September 2027.
When does IBM MQ 9.2 go out of support?
IBM MQ 9.2 LTS reached general availability on 23 July 2020 and entered Extended Support on 30 September 2025. Critical defect support runs to 30 September 2028, with Extended Support available until 30 September 2029.
How long is an IBM MQ LTS release supported?
IBM's published policy is five years of standard support from general availability, with Extended Support purchasable for up to four additional years — and defect fixes only in the first of those extended years. Always confirm the exact dates for your version on IBM's product lifecycle page before making a compliance decision.
How do I check which IBM MQ version I am running?
Run dspmqver on the queue manager host. It reports the version, release, and maintenance level. Check the maintenance level, not just the release — being on 9.2 tells you little if you are several fix packs behind.
Can I buy a support extension for an unsupported IBM MQ version?
Extended Support is a paid IBM offering that covers a defined window past standard end of support, but it is not open-ended and defect fixes are limited to the first year of that window. It is a bridge to an upgrade or migration, not a destination.
What are my options once my IBM MQ version is past support?
Three: upgrade to a supported IBM MQ LTS release, purchase Extended Support as a time-boxed bridge, or migrate the workload to an alternative broker with commercial support. Which is cheapest depends on your total cost of ownership, not just the license line.
