AI-Powered Code Intelligence
CortexIQ traces dependencies across thousands of files and multiple call levels, so you know which components and business functions a change will touch.
Product walkthrough
A simplified run-through of the CortexIQ workflow, step by step.
CortexIQ · Change impact
core-banking / PL/I · commit 4f2a91c
CortexIQ follows one PL/I procedure change through programs, includes and data, sets aside edits that change nothing, and picks only the regression tests on the impact path.
Illustrative CortexIQ change-impact walkthrough on a PL/I core-banking slice: a dependency graph of 24 components in three levels — 9 programs, 8 includes and 7 tables and files. The commit changes the CALC_ACCRUAL procedure in INTCALC.pli: interest was divided by a fixed 365 days; it is now divided by the account currency’s days in the year and rounded to two decimals. Impact ripples out from INTCALC across 8 components, including INTCALC itself: ACCTPOST, INTCALC, STMTGEN, GLREC, ACCRREC, GL_JOURNAL, INT_ACCRUAL, STMT.EXTRACT. Affected business functions: Daily interest accrual, General ledger posting, Customer statements. Context-aware change filtering sets aside 3 non-impactful edits: INTCALC.pli (header comment updated); FEEASSES.pli (reformatted, no logic change); CUSTMNT.pli (unreachable block removed). Selective testing runs 37 of 1,240 regression tests (illustrative figures) across ACCRUAL_DAILY (14), GL_POST_EOD (11), STMT_MONTHLY (12).
Map
Dependencies traced across programs, includes, tables and files.
Change
One procedure, CALC_ACCRUAL, changes its day-count logic.
Assess
Impact ripples out level by level to components and business functions.
Filter
Formatting, comment and dead-code edits are set aside as non-impactful.
Test selectively
Only regression tests on the impact path are selected.
The problem
Decades of PL/I, COBOL and VB6 hide multi-level dependencies, dead code and performance bottlenecks. Without visibility, every change needs slow manual impact analysis — and still risks regression defects in production.
Our approach
Engineers query the graph instead of reading code file by file: a forensic view into the estate that eases the operational cost of maintenance.
Capabilities
Trace application dependencies across thousands of files and multiple call levels.
Identify affected components and business functions before implementing changes.
Distinguish meaningful code changes from non-impactful modifications.
Reduce regression effort while accelerating modernization and migration initiatives.
Bring a module or a recent change from your PL/I, COBOL or VB6 estate. We'll show you its dependency map and the regression tests that actually matter.