AppliedModernization31 min
Application discovery and dependency analysis
Before you change or modernize a mainframe application you need to know what it really contains and what depends on what. Learn to inventory programs, copybooks, JCL, datasets, Db2 tables and transactions, build call graphs and data lineage, find dead code and turn the evidence into a backlog.
What you will be able to do
- Explain why discovery comes before any modernization or major change, and what goes wrong without it
- Build an inventory of programs, copybooks, JCL, datasets, Db2 tables and transactions from static and runtime sources
- Use call graphs, data lineage and impact analysis to scope a change and find dead code safely
- Turn discovery evidence into a prioritised modernization backlog
Lessons
- Why discovery comes first: building the inventoryMainframe applications are often decades old and poorly documented. Discovery means building an evidence-based inventory of every program, copybook, job, dataset, table and…
- Call graphs, data lineage and impact analysisOnce you have an inventory, you relate the pieces: which programs call which, which jobs and programs read and write which data, and what a proposed change will touch.
- Dead code, tools and building the backlogDiscovery usually finds code nobody uses, which can be retired carefully to shrink the estate.
Track your progress and earn a certificate.
Free account, 15 quiz questions for this subject.