An IBM i version upgrade changes the operating-system release. It does not, by itself, replace the Power server. For IBM i 7.6, IBM lists 7.4 and 7.5 as valid source releases and requires Power 10 or later hardware. Those two gates should be checked before anyone treats an AS400 or iSeries version upgrade as a routine install.
Separate the IBM i release from the server refresh
AS400 and iSeries are still common names for active IBM i environments. A search for an AS400 version upgrade may mean an operating-system change, a hardware migration, or both. Give each decision its own record: source and target IBM i releases, current and target machine types, partition and firmware levels, application dependencies, and the reason the business needs the change. The AS400 hardware upgrade guide covers the Power 11 server decision. This page covers the software release decision.
Check the source release before choosing IBM i 7.6
| Starting point | What to investigate | Evidence needed |
|---|---|---|
| IBM i 7.5 | A 7.6 upgrade can be planned if the server and dependencies qualify. | Exact model, firmware, required PTFs, licensed programs, application vendor support, and a tested recovery option. |
| IBM i 7.4 | IBM permits a direct 7.6 upgrade. Review changes introduced in both 7.5 and 7.6. | The 7.5 and 7.6 Memo to Users, discontinued functions, required PTFs, model mapping, and restore evidence. |
| Earlier than 7.4 | No direct 7.6 upgrade. Identify a supported intermediate release and the hardware needed at each stage. | IBM's guidance for the actual source release, application compatibility, entitlements, migration method, and recovery test. |
IBM's 7.6 upgrade index is the source for valid releases and prerequisite checks. The sequence for an older environment cannot be decided from a keyword or a generic chart.
Check the Power model and firmware separately
IBM lists Power 11 and qualifying Power 10 servers for IBM i 7.6, with a minimum FW1060 firmware level for Power 10. Power 9 and earlier are not supported for 7.6. Use IBM's 7.6 hardware guidance and model-to-release map for the actual machine type. A supported processor family is a starting point; the exact model, firmware, partition configuration, and connected components still need verification.
Build the pre-upgrade evidence file
Before scheduling an install, record the source release, machine type, serial number, logical partitions, firmware, installed PTF groups, licensed programs, storage and load-source capacity, application and interface dependencies, installation-media entitlement, and the last successful full-system recovery test. IBM's required PTF notice also calls for additional Licensed Internal Code space before a 7.6 upgrade. Check the current notice for the exact source release and install method rather than copying an old PTF list into a runbook.
Use IBM's Pre-Upgrade Verification Tool and Memo to Users references as part of that evidence file. Then have the application owners verify product support, third-party dependencies, and business validation steps. A version that installs is not automatically a version the business can use.
Work through one real planning contradiction
Consider an illustrative shop running IBM i 7.3 on a Power 9 server that wants 7.6. The release is below IBM's valid direct-upgrade source, and the server is outside IBM's 7.6 hardware support. A hardware quote alone does not solve the release sequence; an operating-system plan alone does not solve the server gate. The team needs a supported intermediate-release decision, target-model check, application testing plan, recoverable save, and measured cutover window. That is a planning example, not a claim that any specific migration has been completed.
Put the cutover and rollback in measurable terms
Define the install method, owner for each dependency, expected downtime, recovery checkpoint, business acceptance test, and the condition that triggers rollback. Test the restore to the intended recovery environment and record the observed time. A calendar promise such as "one weekend" is not evidence. The recovery test is.
If the project also includes a server move, use the iSeries server refresh guide and the Power 11 hardware migration guide. For recovery dependencies, use the IBM i disaster-recovery guide. A planning review should connect all three decisions before anyone asks for a final quote.
FAQ
Can IBM i 7.3 upgrade directly to IBM i 7.6?
No. IBM lists 7.4 and 7.5 as valid upgrade sources for 7.6. An older environment needs an IBM-supported intermediate-release and hardware plan.
Does moving to Power 11 automatically upgrade IBM i?
No. The new server and the IBM i release are separate decisions. Plan the release, licensed programs, applications, migration method, and recovery test alongside the hardware change.
Can a Power 9 server run IBM i 7.6?
No. IBM's 7.6 hardware guidance supports Power 11 and qualifying Power 10 servers, not Power 9 or earlier.