IBM iSeries 7.3 End of Life September 30, 2023 Action Plan

What Happens on September 30, 2023

IBM iSeries 7.3 reaches end of life on September 30, 2023. After that date, IBM will no longer provide security patches, bug fixes, technical support, or service level agreements for this release. Systems running 7.3 will continue to operate, but any newly discovered vulnerabilities will remain unpatched, and hardware or software failures will have no vendor escalation path.

For most organizations still running iSeries 7.3 in production, a full migration to a supported release before the end of September is no longer realistic. The remaining time is better spent on damage control: understanding your exposure, hardening what you can, and ensuring continuity of support after the vendor exits.

Week 1-2: Complete System Inventory

Start with a definitive list of every system running iSeries 7.3. Include:

• Hostname, IP address, and physical or virtual location
• Business applications and services hosted on each system
• Data classification (customer records, financial data, regulated information)
• Network zone (DMZ, internal, isolated)
• Upstream and downstream dependencies

This inventory will guide every decision that follows. Systems processing payment card data or personal health information carry different risk profiles than internal development boxes. Systems exposed to the internet require immediate attention; air-gapped test environments may safely defer.

Week 3-4: Assess and Isolate High-Risk Systems

For each 7.3 system, evaluate:

• Can this workload be migrated to a supported release before September 30? If the application is vendor-supported, containerized, or already tested on iSeries 7.4 or later, prioritize the move.
• Can this system be taken offline or decommissioned? Legacy reporting tools and redundant failover nodes are common candidates.
• Must this system remain in production past EOL? If yes, document the business justification and plan accordingly.

For systems that must stay online, reduce the attack surface:

• Remove or disable unused services, accounts, and open ports
• Restrict network access using firewalls and VLANs
• Enable logging and integrate with your SIEM
• Apply all available patches before September 30

Week 5-6: Document Risk and Notify Stakeholders

Prepare a formal risk assessment for leadership, auditors, and your insurance carrier. Include:

• Number of systems remaining on 7.3 after EOL
• Business criticality and data sensitivity of each system
• Specific compliance frameworks affected (PCI-DSS, HIPAA, SOC 2)
• Mitigation controls in place (network isolation, monitoring, compensating security measures)
• Timeline for final migration or decommissioning

Many compliance standards do not explicitly forbid unsupported software, but they do require documented risk acceptance and compensating controls. Cyber insurance policies may have different thresholds. Clarify your obligations early.

Week 7-8: Secure Third-Party Support

Once vendor support ends, you have two options: operate without any safety net, or engage a third-party support provider. Third-party support for IBM iSeries can provide:

• Security patches for newly discovered vulnerabilities
• Bug fixes and troubleshooting assistance
• Extended coverage while you complete a staged migration
• Break-fix support for underlying hardware

A third-party agreement should be in place before September 30, 2023. Negotiating and onboarding a new vendor takes time, and you do not want a gap in coverage the day IBM's SLAs expire. Review contract terms carefully: confirm that security patching is included, clarify response times, and ensure the provider has experience with your specific iSeries workloads.

Week 9-12: Final Preparations

In the final weeks before EOL:

• Apply all remaining IBM patches and PTFs
• Take fresh backups and verify restore procedures
• Update runbooks and escalation procedures to reflect the new support arrangement
• Schedule a post-EOL review meeting to assess what worked and what needs adjustment

On October 1, 2023, IBM's support portal will no longer accept new cases for iSeries 7.3. Your organization must be ready to respond to incidents without vendor assistance—or with a third-party provider ready to step in.

Why Organizations Stay on Unsupported Releases

Migration delays are common and often rational. Application dependencies, budget cycles, and resource constraints all play a role. The iSeries platform is known for stability and backward compatibility, which can make the risk of staying on an older release feel manageable—until a zero-day vulnerability or hardware failure forces a crisis upgrade.

Third-party support bridges that gap. It allows you to maintain security and operational continuity on your own timeline, without the pressure of a forced migration driven by an arbitrary vendor EOL date.

What Comes Next

IBM iSeries 7.3 will not stop working on September 30, 2023. But the safety net disappears. Every day after EOL increases your exposure to unpatched vulnerabilities, compliance findings, and operational risk.

If your organization will have iSeries 7.3 systems in production after September 30, take action now. Complete your inventory, harden your exposure, document your risk posture, and contact a third-party support provider to ensure continuity when IBM's coverage ends. The next 90 days will determine whether your EOL transition is controlled or chaotic.