IBM i Upgrade Dependency Inventory

The Upgrade Checklist Is Not The Project

A checklist tells the team what to consider. A dependency inventory assigns the work, names the owner, and exposes the items that can block a real IBM i upgrade or hardware migration.

This is the next intent step for buyers who already know they need to move toward a supported IBM i release. The driver may be hardware refresh, security, or vendor support.

Inventory Platform Dependencies

Start with the platform dependencies that decide whether the upgrade is straightforward or blocked. IBM's upgrade planning guidance points buyers toward compatibility and pre-upgrade tooling because these details matter before the window is approved.

• IBM i release and Technology Refresh level
• PTF groups
• Firmware
• HMC level
• VIOS if present
• Backup method
• Storage and tape
• Printer and output dependencies
• Scheduled jobs
• System values that affect application behavior

Inventory Application And ISV Dependencies

List every application dependency that touches the partition. For each dependency, record the owner and the status that could block the cutover. The point is not a larger spreadsheet. It is reducing surprise.

• Packaged applications
• Custom RPG or COBOL applications
• Java dependencies
• ODBC or JDBC connections
• EDI paths
• Warehouse interfaces
• Report extracts
• APIs
• Document workflows
• Security tools
• Vendor support status
• Version and license key behavior
• Test evidence and rollback expectation

Decide The Test Sequence

Testing should follow business priority, not file names. Start with the workflows that create revenue or operational risk.

Each test should have a pass condition and a named business reviewer. If nobody can say what success looks like, the upgrade is not ready for that workflow.

• Create revenue
• Ship product
• Close finance
• Process EDI
• Run payroll
• Satisfy compliance

Write Rollback Before Cutover

Rollback planning should be written before the cutover window is approved. A rollback plan is not a lack of confidence. It is what makes a technical upgrade acceptable to the business.

• Last safe point
• Backup state
• Save or snapshot method
• Decision deadline
• Communication path
• Who can stop the cutover

Common questions about this Version Upgrade topic.

What belongs in an IBM i upgrade dependency inventory?

Include every item that can block the project.

• IBM i release
• PTF groups
• Firmware
• HMC
• VIOS
• Backup
• ISV software
• Custom applications
• Java
• ODBC
• EDI
• Printers
• Schedulers
• Reports
• APIs
• License keys
• Owners
• Test status
• Rollback requirements

When should rollback planning happen?

Rollback planning should happen before the cutover window is approved. The team should know the last safe point and the deadline for deciding whether to continue or reverse the change.

Sources

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