Build database documentation for IBM i that ties each file and its fields to the RPG programs that read or update them, written from your own source code.
See what a call graph of your RPG library shows on IBM i, from the jobs that reach each program to the programs nothing calls, built from your own source.
Build a knowledge transfer plan for IBM i from a plain-English description of every RPG program, and spend senior developer time on what only he knows.
Technology due diligence on a company that runs IBM i starts with the RPG source. See what to ask the seller and how the source stays on the target’s network.