IBM iSeries 7.4 EOL September 30, 2026 Action Plan

The EOL Deadline Is September 30, 2026 — Here Is Your Action Plan for IBM iSeries 7.4

With IBM iSeries 7.4 reaching end of life (EOL) on September 30, 2026, most organizations no longer have enough time for a full migration to a newer release before the deadline. This article walks through what changes on that date, what the remaining three months are best used for, and a concrete week-by-week checklist to close out the lifecycle gap without panic.

What Changes on September 30, 2026

On the EOL date, vendor support for IBM iSeries 7.4 ends entirely. This is not an LTS release — the latest version in the line is 7.4.0, and no further patches, fixes, or security updates will be issued by IBM. After that date:

• No more OS patches or PTFs — Any unpatched vulnerabilities will remain unaddressed.
• No vendor SLAs — If the system crashes or encounters a defect, IBM will not respond under a support agreement.
• No security fixes — CVEs disclosed after September 30, 2026 will not be patched for 7.4.
• Compliance exposure — Auditors and cyber insurers will treat an unsupported OS as a risk exception or non-compliance finding.

Because a full migration to IBM i 7.5 (or higher) in roughly three months is unrealistic for most estates, the focus must shift to risk containment, documentation, and transitioning to third-party support before day one after EOL.

Week-by-Week Action Checklist (13 Weeks Remaining)

Weeks 1-2: Inventory and Baseline

• Identify every partition and LPAR running iSeries 7.4. Use native commands (DSPRSCAFP, DLTOBJ, or the HMC) to list all systems.
• Record the current PTF group level for each system. Document which critical applications (ERP, database, file serving) depend on each instance.
• Flag any system that processes payment card data (PCI), protected health information (HIPAA), or personally identifiable information (PII) — these will require additional hardening steps.

Weeks 3-4: Vulnerability and Exposure Assessment

• Compare the recorded PTF level against the last publicly available IBM security bulletins for 7.4. Identify any unmitigated CVEs.
• For each identified vulnerability, determine if a workaround exists (e.g., disabling a service, tightening firewall rules, or applying an i5/OS network filter).
• Document the risk acceptance rationale for each system you plan to keep on 7.4 past EOL.

Weeks 5-8: Harden and Isolate

• Apply all remaining PTFs that IBM still provides before the cutoff. Prioritize security PTFs over functional fixes.
• Restrict network access to the 7.4 partitions: remove direct internet connectivity (or route through a DMZ with a reverse proxy), disable unneeded services (FTP, Telnet, QNTC, etc.), and enforce encrypted protocols (SSH, SFTP, TLS 1.2+).
• Configure network segmentation — place 7.4 partitions in a separate VLAN with a strict access control list. No inbound traffic except from a management jump box.
• Enable logging to a SIEM or a centralized syslog server. Ensure audit settings include enough detail for post-EOL forensic review.

Weeks 9-10: Document for Auditors and Insurers

• Create an EOL risk register that lists each system, its business owner, its last PTF date, and its exposure category (high/medium/low).
• Write a brief memo for internal audit and the CFO explaining why a full migration was not feasible, and describing the compensating controls (isolation, hardening, monitoring, third-party support).
• Review your cyber insurance policy: many carriers require timely patching. Some offer an exemption if the systems are under a third-party support contract. Share the support contract evidence with your broker.

Weeks 11-12: Line Up Post-EOL Support

• Engage a third-party support provider for IBM iSeries 7.4 before September 30. Third-party support can continue to supply security patches, bug fixes, and vendor-level SLAs for the 7.4 platform after IBM stops. This is not an advisory-only plan — it covers the same hardware and software defects the vendor would have.
• Confirm the support start date aligns with the EOL date (September 30, 2026). You want coverage beginning day one, not after a lapse.
• Ensure the provider includes access to their own PTF or patch library (some third-party vendors maintain curated patch sets for OS and licensed programs).

Week 13: Pre-EOL Verification and Communication

• Run a final check that all systems are hardened, isolated, and logged.
• Send a status report to IT leadership and audit, confirming that the inventory is complete and compensating controls are in place.
• Test that the third-party support contact info and incident process are published to your operations team.

How Third-Party Support Bridges the Gap

Third-party support for IBM iSeries 7.4 keeps the system safely in operation beyond the vendor's end-of-support date. Providers like 3rd Party Support offer:

• Security patches for newly disclosed CVEs, including those that IBM will not patch for 7.4 after September 30.
• Bug fixes for OS and licensed program defects, with published SLAs (e.g., 4-hour response, next-business-day resolution).
• Hardware support for IBM Power Systems running 7.4 — same scale, same replacement parts, without requiring an IBM maintenance contract.
• Compliance reassurance — auditors and insurers generally accept a valid third-party support contract as a compensating control for an unsupported OS.

Rather than rushing a risky migration in three months, the prudent path is to inventory, isolate, harden, document, and secure a support contract before the EOL date. Use the time you have left to make that transition clean.

For more details on IBM iSeries lifecycle and support options, see the vendor page. To discuss a support contract for your 7.4 estate, contact us.