Find the IBM i release and model before choosing steps
Record the release from the Display Software Resources command, DSPSFWRSC. Use DSPPTF to review installed fixes and WRKPTFGRP for PTF groups. Record the hardware machine type and model from the system label or management inventory. Repeat the software check for every logical partition; one server can host different releases.
A technology refresh adds capabilities within a release. It does not turn IBM i 7.3 into 7.4. Match the release and required fixes to the exact hardware configuration.
Supported direct IBM i OS upgrade steps
These are software upgrade starting releases, not promises that every machine running them can install the target. A migration using previous-release recovery is a separate documented procedure.
| Target release | Documented source releases | Hardware decision |
|---|---|---|
| IBM i 7.6 | IBM i 7.4 or IBM i 7.5 | Use a listed Power 10 or Power 11 IBM i configuration with required code. |
| IBM i 7.5 | IBM i 7.3 or IBM i 7.4 | Use an eligible Power 9, Power 10 or Power 11 configuration. |
| IBM i 7.4 | IBM i 7.2 or IBM i 7.3 | The system must support 7.4; Power 7 and earlier do not. |
Skipping an intermediate OS release still means reviewing its application changes and discontinued functions. For example, a 7.4-to-7.6 upgrade needs the relevant changes in both the 7.5 and 7.6 memos.
IBM i 7.6
Hardware context: Power 10 and Power 11 models listed for IBM i.
Already on 7.6: maintain the required code and check application support before changing hardware.
Treat a hardware move as a migration even when the OS release stays the same.
Match this release to your current model · Plan the release and hardware sequence
IBM i 7.5
Hardware context: Selected Power 9, Power 10 and Power 11 models.
7.5 is a valid source for a 7.6 upgrade after prerequisites are met.
Power 9 does not run 7.6; pair that OS goal with an eligible hardware replacement.
Match this release to your current model · Plan the release and hardware sequence
IBM i 7.4
Hardware context: Selected Power 8, Power 9, Power 10 and Power 11 models.
7.4 is a valid source for a 7.5 or 7.6 upgrade on eligible hardware.
Power 8 stops at 7.4. Moving beyond that release requires replacement hardware.
Match this release to your current model · Plan the release and hardware sequence
IBM i 7.3
Hardware context: Eligible Power 7 rack/tower, Power 8 and selected later models; not Power 11.
7.3 can be an upgrade source for 7.4 or 7.5 when the system supports the destination release.
A Power 7 system cannot run 7.4; a Power 10 S1012 cannot run 7.3.
Match this release to your current model · Plan the release and hardware sequence
IBM i 7.2
Hardware context: Selected Power 6, Power 7, Power 8 and Power 9 models.
7.2 can be an upgrade source for 7.4 on eligible hardware.
Power 6 and the listed Power 7 blades/Flex nodes stop at 7.2; they cannot perform that OS step in place.
Match this release to your current model · Plan the release and hardware sequence
IBM i 7.1
Hardware context: Older eligible models; selected S922/E980 only through a special offering.
Treat the source as a legacy upgrade assessment. Review supported intermediate releases and program compatibility first.
7.1 is not a source for a direct in-place 7.5 or 7.6 upgrade. Newer hardware generally cannot boot this source release.
Match this release to your current model · Plan the release and hardware sequence
IBM i 6.1, i5/OS V5R4 and earlier
Hardware context: IBM i 6.1 and i5/OS V5R4 or earlier, with exact model and machine-code requirements.
Identify the actual installed release, recovery media and program-conversion requirements before selecting steps.
Preserve available source code and vendor installation media. A save of the old system alone does not establish recoverability on a current release.
Match this release to your current model · Plan the release and hardware sequence
A release can run without being in standard support
IBM’s hardware mapping and the service contract answer different questions. A release shown as compatible can already be outside standard support. Service Extension has its own coverage and terms.
| Release | Dated planning context |
|---|---|
| IBM i 7.4 | Standard support changed September 30, 2026. IBM lists Service Extension from October 1, 2026 through September 30, 2029; confirm contract and product coverage. |
| IBM i 7.3 | IBM lists extended Service Extension from October 1, 2026 through September 30, 2028; confirm the offering for the installed products. |
| IBM i 7.2 | The listed extended Service Extension period ended April 30, 2026. Confirm any separate arrangement rather than assuming coverage. |
| IBM i 7.5 and 7.6 | Check IBM’s current lifecycle notice and the software maintenance entitlement for the actual system. |
Prepare IBM i before the release upgrade
- Required PTFs for IBM i 7.6 identify fixes for the supported source releases.
- Required PTFs for IBM i 7.5 cover install preparation and internal-code space.
- Required PTFs for IBM i 7.4 retain media and source-release qualifications.
- IBM’s install and recovery reference links the release-specific manuals and memos.
Use IBM’s current Pre-Upgrade Verification tool and resolve its findings. Check free space for Licensed Internal Code, software keys and vendor application support. Rehearse with a usable save before the production change.
Build the rehearsal and rollback plan · Ask Midland to review your release sequence
Sources and compatibility checks
Technical guidance checked October 21, 2026. A hardware release mapping describes which releases can run; support coverage and software entitlement are separate checks.