AS400 cloud migration moves the machine and leaves your RPG code unchanged. Map your copy members and dependencies before an IBM i vendor prices the work.
AS400 end of life is three separate clocks. Hardware service, IBM i release support and your last RPG developer each price a different migration project.
AS400 documentation is only useful when a developer can check it against the member. How to generate descriptions from RPG source and read the confidence flags.
Application dependency mapping on IBM i stops at the compiled object. Copy members vanish at compile time, and DSPPGMREF never removes a stale entry it stored.
Air gapped AI for IBM i source code: what the install requires, what crosses the boundary, and the evidence your security team collects to prove nothing left.
