IBM z/OS 2.5 End of Support: September 30, 2026 — the Three-Year Paid Extension, and the Move to 3.1 or 3.2
z/OS 2.5 reaches end of support on September 30, 2026. IBM's lifecycle entry for 5650-ZOS says it plainly — general availability September 30, 2021, withdrawn from marketing January 29, 2024, and “Transition to Extended/Sustained or End of Support” on September 30, 2026. That word “transition” is the commercially important one: z/OS follows IBM's Enhanced lifecycle policy, which pairs the five-year standard window with an optional paid extension of up to three years. So the date is real, but so is the bridge — at a price.
The mainframe estate is the last place to run past a support date casually: it is where the regulated workloads live, and where auditors look first. This page gives the verified dates for every current release, what the paid extension does and does not cover, the upgrade path, and the decision framework.
Key Dates at a Glance
- z/OS 2.5: released 2021-09-30; end of support 2026-09-30
- z/OS 2.4: end of support 2024-09-30
- z/OS 2.3: end of support 2022-09-30
- z/OS 3.1: released 2023-09-29; no announced end of support
- z/OS 3.2: released 2025-09-30; no announced end of support
z/OS EOL Risk Scores
We publish an EOL Risk Score (0–100) for every tracked version — lifecycle recency, attack surface, KEV exposure, extended-support availability — recalculated at every build. z/OS scores start low relative to internet-facing platforms: the attack surface is narrow by design and vendor extended support exists. The lifecycle clock is still the lifecycle clock.
| Release | EOL Risk Score | What drives it |
|---|---|---|
| z/OS 2.5 | 25 | End of support September 30, 2026 — the recency factor is climbing; IBM extension available. |
| z/OS 3.1 | 10 | Supported, no announced end date; the platform baseline. |
How the z/OS Lifecycle Works
- A release every two years, at the end of September: 2.4 (2019), 2.5 (2021), 3.1 (2023), 3.2 (2025).
- Enhanced (E) policy: a minimum of five years of standard support, then an optional paid extension of up to three years. 2.5's five years end September 30, 2026; the extension can carry defect support to 2029.
- Coexistence: IBM supports three consecutive releases coexisting in a sysplex, which is what makes rolling upgrades practical — 2.5, 3.1 and 3.2 can run side by side during the migration.
- Predictability is the point: like the platform itself, the dates never surprise. z/OS 3.1's end of support is expected around 2028 and 3.2's around 2030 on the same arithmetic, though neither is announced — and we publish only announced dates as facts.
The Paid Extension: What It Buys
IBM's extension (sold through IBM's software support services alongside offerings like SoftwareXcel and Support Line, which the lifecycle page lists as eligible service for 2.5) continues defect and usage support after the standard window. Three things to know before treating it as the plan: it is priced per year on mainframe terms — typically material next to the MLC/software bill; it does not restore currency — new hardware, middleware and ISV versions certify against 3.x, not 2.5; and it ends. Three years from September 2026 is September 2029, and the upgrade still has to happen. It is the right tool exactly when the 3.x migration is scheduled but will not land by September — and the wrong one as a substitute for scheduling it.
The Move to 3.1 or 3.2
Both current releases are supported migration targets from 2.5, and IBM's upgrade workflows document each path. The operating-system upgrade itself is the well-trodden part; the schedule is set by everything around it: ISV product certifications (the usual long pole), any hardware currency requirements, sysplex rolling-upgrade windows, and the testing calendar of the applications on top. Going straight to 3.2 buys the longest runway; 3.1 is the smaller step for estates with conservative ISV stacks. Either way, teams that have not started by now are choosing between a compressed 2026 project and buying the extension — which is precisely the decision IBM's pricing anticipates.
How to Check Your z/OS Release
D IPLINFOfrom the console — the release is in the response (e.g.z/OS 03.01.00).SYSVAR('SYSOPSYS')in REXX, or the fields in SDSF; your SCRT/capacity reports also state it.
Anything reporting 02.05 has a September 30, 2026 deadline; 02.04 and below are already unsupported. Every release is on the z/OS product page with live status, and the EOL Checker answers for the rest of the stack around it — the Db2, IMS, CICS and MQ versions on the same footprint each have their own clocks (see Db2 and MQ).
Your Options, Honestly Compared
- Upgrade to 3.1/3.2 before October. The clean exit. If ISV certifications are done, a 2.5 → 3.x upgrade inside a year is normal mainframe practice.
- Buy the IBM extension and schedule the upgrade. The honest bridge: defect support to as late as 2029, at a price that concentrates the mind. Budget it as a migration line-item, not a subscription.
- Stay unsupported. On this platform, effectively not an option: no PTFs, no security/integrity APAR fixes, and an audit finding in every regulated framework the mainframe exists to satisfy.
Frequently Asked Questions
When does z/OS 2.5 reach end of support?
September 30, 2026 — IBM's lifecycle page for z/OS 2.5.0 (5650-ZOS) lists 'Transition to Extended/Sustained or End of Support: 30-Sep-2026' under announcement AD25-0071. z/OS 2.5 became generally available September 30, 2021 and was withdrawn from marketing January 29, 2024.
Can I buy support for z/OS 2.5 after September 2026?
Yes. z/OS follows IBM's Enhanced (E) lifecycle policy: a minimum of five years of standard support with an optional paid extension of up to three years. IBM sold the same extension for z/OS 2.4 (end of support September 30, 2024) and earlier releases. It is priced as an add-on service and covers defect support — a bridge for estates mid-upgrade, not a new baseline.
Which z/OS releases are supported right now?
z/OS 3.2 (GA September 30, 2025) and z/OS 3.1 (GA September 29, 2023) have no announced end-of-support dates; z/OS 2.5 is supported until September 30, 2026. IBM ships a new z/OS release every two years, at the end of September, and each release gets at least five years of support — so 3.1's end of support is expected around 2028 and 3.2's around 2030, but neither is announced.
What is the upgrade path off z/OS 2.5?
To z/OS 3.1 or z/OS 3.2. IBM's coexistence and fallback policy supports three consecutive releases, so 2.5 systems can share a sysplex with 3.1 and 3.2 during a rolling upgrade, and IBM's upgrade workflows document the move from 2.5 to each. The gating items in practice are ISV software certification, hardware currency, and the change-window calendar — not the operating system itself.
What happens if we simply stay on z/OS 2.5?
After September 30, 2026, no more PTFs or security/integrity fixes under standard support — on the platform that runs the workloads auditors care most about. Without the paid extension, staying is running an unsupported mainframe OS; with it, the clock only extends to 2029. Regulated industries (the bulk of the z/OS installed base) should treat the date as a compliance boundary, not a suggestion.
How do I check which z/OS release we run?
From TSO/console: D IPLINFO shows the release (e.g. z/OS 03.01.00). In SDSF or via SYSVAR('SYSOPSYS') in REXX. Operationally your capacity/monthly reports (SCRT) also state it. The version string maps directly to the dates above — anything reporting 02.05 has a September 30, 2026 deadline.
Related Resources
- z/OS product page — live status, dates and risk scores for every release
- IBM enterprise software end-of-life overview · Db2 · IBM MQ · IBM i · AIX
- EOL Watch · EOL Checker · EOL Risk Score methodology