AS400 Learning Center

AS400 End of Life ... Is Your System Still Supported?

An AS400 nameplate does not tell you when support ends. Check your Power server and IBM i release to find the deadline that actually affects your business.

Published Updated

If you know the IBM i release, check it first. IBM i 7.6 and 7.5 are current releases. IBM i 7.4 is in service extension. IBM i 7.3 is in extended service extension. IBM i 7.2 is past its listed extension.

AS400 end of life can still mean the original hardware, the IBM i release, the Power server, or the business application. The release check gives you the first answer. The rest of this guide shows which layer to check next.

IBM i Release Check

Is Your IBM i Release Still Supported?

Choose the installed release for its current IBM lifecycle state and the next move to verify.

Current release

Current release

IBM lists IBM i 7.6 as current with no announced change-in-service date.

Next move

Verify current PTF groups, application certification, and the IBM Power model before planning the next upgrade.

Checked November 12, 2026 ... IBM i release life cycle

Does AS400 End of Life Mean Your System Stops Working?

AS400 as an original hardware product family is past its normal lifecycle. AS400 as a name for IBM i workloads is not dead. Many organizations still run business-critical applications from the AS400 lineage on supported IBM i releases and modern IBM Power hardware.

That is why a useful end-of-life review separates the brand name from the current technical stack. A workload called AS400 by the business may actually be IBM i 7.4, 7.5, or 7.6 on a Power 9, Power 10, or Power 11 server.

Which Part of Your AS400 Is Out of Support?

There are four lifecycle layers to check:

  • Hardware: the physical server model, parts availability, firmware support, adapter support, HMC compatibility, and warranty or maintenance status
  • Operating system: the IBM i release, Technology Refresh level, PTF currency, and whether standard support or service extension applies
  • Application: ERP, custom RPG or COBOL code, third-party packages, database structures, interfaces, and vendor certification
  • Operational stack: backup tooling, high availability, tape or SAN support, terminal access, printers, monitoring, and security controls

An environment can be healthy at one layer and exposed at another. For example, a stable application can still be running on an IBM i release that has entered service extension, or on hardware that limits the upgrade choice.

Check the IBM i Release You Actually Run

IBM publishes IBM i lifecycle information by release, not by the old AS400 label. Checked November 12, 2026, IBM lists IBM i 7.6 and IBM i 7.5 as current releases with change-in-service dates not yet announced. IBM i 7.4 is in service extension through September 30, 2029. IBM i 7.3 is in extended service extension through September 30, 2028.

That means a company asking whether AS400 is end of life should first identify its IBM i release. The same legacy term can describe a system with very different risk depending on whether it is running 7.3, 7.4, 7.5, 7.6, or an older unsupported release.

When Your Power Server Cannot Run the IBM i Release You Need

Even when an IBM i release has support coverage, the hardware may become the limiting factor. Older Power generations eventually stop supporting newer IBM i releases. IBM's platform support details show that new Power 11 systems require specific IBM i 7.6, 7.5, or 7.4 levels, while older releases do not become the planning baseline for current-generation hardware.

If the current server cannot move to a supported target release, the end-of-life issue becomes a hardware refresh discussion. Start with AS400 Model History and IBM Power Systems Overview to translate old model names into a modern upgrade option.

When an AS400 Upgrade Cannot Wait

Common triggers include unsupported IBM i releases, expired hardware maintenance, weak backup confidence, aging disk, unsupported tape or adapters, missing PTF discipline, auditors asking about security fixes, application vendor certification gaps, and a shrinking internal skill base. None of those automatically means migrate off IBM i. Often the best answer is to keep the workload, refresh the hardware, upgrade IBM i, and modernize the access layer.

For support detail, read AS400 Support. For the current release support table, read IBM i Support Status.

Running a Power 720? Check the Full Model Number.

8202 is only part of the answer. The E4B, E4C or E4D suffix changes which support date applies to your Power 720.

Use the Power 720 replacement checklist to check what your contracts cover and what a replacement must run. Get that settled before a hardware problem forces the buying decision.

Frequently Asked Questions

Is AS400 end of life?
The original AS/400 hardware line is end-of-life legacy hardware. The modern IBM i platform in the same lineage is still active when it runs on supported IBM Power hardware with a supported IBM i release.
What replaced AS400?
AS400 evolved into iSeries, then System i, and then IBM i running on IBM Power Systems. IBM did not replace it with a separate non-IBM platform.
Does AS400 end of life mean I must migrate off IBM i?
No. Many organizations handle lifecycle risk by upgrading IBM i and refreshing IBM Power hardware while preserving the core RPG, COBOL, DB2 for i, and business application stack.
What should I check first for AS400 lifecycle risk?
Start with the IBM i release, machine type and model, serial number, PTF level, hardware maintenance status, backup method, application vendor status, and whether the target IBM i release is supported on the current server.