Anyone used ADDI / similar before a COBOL modernization?

We are scoping a modernization on a messy IBM Z estate - COBOL, CICS, JCL, DB2. Docs are thin. Manual call-chain hunting is eating the calendar.

Looking for what people actually use for dependency / impact analysis before touching data structures. ADDI came up in a vendor call. Also curious if anyone combines static analysis with runtime call tracing (IGZPROUT, CICS stats, etc).

Not looking for a sales pitch. What worked, what lied to you.

We ran ADDI on a pilot app. Useful for DB2 table and CICS transaction maps. Still missed dead code paths that only fire on rare error conditions.

Static analysis shows what could run. Runtime shows what did run. You need both or you will delete something that only abends once a year.

For batch we monitored which cataloged procs and load modules actually executed over a few months. For CICS, shutdown stats (you can get them without a real shutdown) listed what loaded. Cheap leading indicators for obsolete stuff.

Good framing. We will keep a runtime harvest running in parallel with whatever discovery tool we pick. Appreciate the caution on "never executed = obsolete."