IBM i Modernization Software

What should we test before moving Power 9 applications to Power 10 or Power 11?

Test the supported IBM i release path first, then map every dependency around the application.

Answer

  • Packaged ERP
  • Custom RPG and COBOL programs
  • Java jobs
  • ODBC and JDBC paths
  • EDI
  • Document management
  • Barcode workflows
  • Reports
  • Schedulers
  • Monitoring
  • Security tools
  • Backup software
  • Printers
  • Output queues
  • License keys

Each dependency should be marked go, fix first, or defer. That removes buying friction because stakeholders can see which issues are proven, which need remediation, and which are not blockers.

Back to IBM i Modernization Software

More IBM i Modernization Questions

Related Reading

IBM i Operating System Versions Guide

How to compare IBM i operating system versions, release support, Power 10 and Power 11 compatibility, and upgrade readiness before a hardware move.

IBM i API Integration Buyer's Guide

A practical planning guide for IBM i teams connecting legacy systems to modern applications safely through APIs, orchestration, and governed data exposure.

IBM i Database Tools Buyer's Guide

A practical planning guide for IBM i teams improving Db2 for i access, reporting, governance, modernization readiness, and developer productivity.

Preferred Partners

API Integration Preferred Partners

Profile for the partner types that help IBM i buyers design integrations, publish APIs, and connect IBM i systems to modern applications safely.

IBM i Security Preferred Partners

Profile for the partner types buyers usually need when IBM i security, MFA, auditing, and access governance projects become active.