AS400 Version Upgrade Planning Checklist

Confirm Why The Upgrade Is Happening

Version upgrades happen for different reasons: IBM support timing, Power hardware compatibility, security requirements, vendor certification, application modernization, or audit pressure. The reason matters because it defines the deadline and testing depth.

A support-date upgrade may have more timing pressure. A hardware-migration upgrade may have more firmware and HMC dependencies. A security-driven upgrade may need stronger evidence and post-upgrade controls.

Build The Inventory

The minimum inventory includes IBM i release, PTF groups, Technology Refresh level, firmware, HMC, LPAR layout, backup tools, HA/DR tools, security software, job scheduler, EDI, ERP, custom programs, ODBC connections, Java levels, and external integrations.

This inventory should be built before the project schedule is promised. It is the only way to see which dependencies can delay the upgrade.

Test What The Business Uses

Upgrade tests should map to real workflows. Nightly batch, printing, EDI, order entry, inventory updates, finance close, backups, role swaps, and reporting should be validated by the people who understand them.

Technical success is necessary, but business workflow success is the actual project outcome.

Protect The Cutover

A version upgrade needs a current backup, restore confidence, communication plan, rollback criteria, after-hours support coverage, and a post-upgrade checklist. The team should know what must be true before the system is released to users.

The more business-critical the workload, the less acceptable it is to improvise after the IPL.

Common questions about this Version Upgrade topic.

What should be checked before an AS400 version upgrade?

Check current IBM i release, target release support, PTF groups, firmware, HMC, backups, ISV products, application dependencies, integrations, test workflow, and rollback plan.

Can an IBM i version upgrade affect third-party software?

Yes. Backup, HA, security, job scheduling, EDI, reporting, ERP, and integration tools may need compatibility checks, updates, or license re-keys before the operating system move.

Sources

• IBM i release life cycle
• IBM i 7.6 hardware planning