PL/I
Procedures, calls and includes across .pli, .pl1 and .pls source.
CortexIQ · AI-Powered Code Intelligence
CortexIQ maps file- and function-level dependencies across PL/I and VB6 code, classifies the impact of every change and explains it in plain English — before it ships.
- Proven on a core banking estate of more than 10M lines of PL/I
Proven results
- lines of PL/I code analyzed
- >10M
- less manual impact-analysis effort
- up to70%
- AI-driven features in one platform
- 8
What it reads
Upload files or one ZIP. CortexIQ detects the language and picks the right analyzer.
-
-
VB6
Modules, forms and classes across .bas, .frm, .cls and related files.
-
Coded UI tests
C# Coded UI and SpecFlow suites, ready to move to Playwright.
-
Cypress tests
Cypress specs, Cucumber steps, commands and fixtures, ready to move to Playwright.
-
COBOL & copybooks (Roadmap)
Dependency and impact analysis for COBOL programs, with copybook resolution.
Product walkthrough
A simplified run-through of the CortexIQ workflow, step by step.
CortexIQ · Change impact
core-banking / PL/I · commit 4f2a91c
Illustrative demo
Sample data · not a client result
CortexIQ maps a PL/I slice across procedures and programs, classifies each changed function as Logic, Log or No Impact, flags the direct callers of the logic change as downstream impact and explains it all in plain English.
Illustrative CortexIQ change-impact walkthrough on a PL/I core-banking slice: a function-level dependency graph of 9 procedures and a file-level graph of 15 files — 8 programs and 7 includes. 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. A second edit, in STMT_MONTHLY (STMTGEN.pli), changes a comment only. CortexIQ classifies CALC_ACCRUAL as Logic Impact and the comment-only edit as No Impact, and sets the comment-only edit aside. It then flags the direct callers of CALC_ACCRUAL as downstream impact: ACCRUAL_DAILY in ACCTPOST.pli (high risk) and POST_LEDGER in GLPOST.pli (medium risk). The plain-English impact report for the reviewer reads: CALC_ACCRUAL now uses the currency’s days in the year, not a fixed 365, and rounds to two decimals, so accrued interest changes. Review its direct callers ACCRUAL_DAILY (high risk) and POST_LEDGER (medium risk). STMT_MONTHLY: comment-only edit, no impact. Result: 3 of 9 functions affected, comment-only edit set aside (illustrative figures).
Map
Dependencies traced across procedures and programs.
Change
One procedure, CALC_ACCRUAL, changes its day-count logic. A second edit elsewhere is comment-only.
Classify
CALC_ACCRUAL is Logic Impact; the comment-only edit is No Impact and set aside.
Assess
The direct callers of CALC_ACCRUAL, ACCRUAL_DAILY and POST_LEDGER, are flagged as downstream impact, with risk levels.
Explain
A plain-English impact report is written for the reviewer.
How it works
- 01 You
Upload
Drop in source files or a ZIP. CortexIQ detects PL/I, VB6, Coded UI or Cypress and picks the analyzer.
- 02 CortexIQ Mapper
Map
Builds file- and function-level dependency graphs, with fan-in, fan-out and centrality metrics.
- 03 You
Change
Edit code in the browser. The original and the last five versions are kept, and every change is tracked.
- 04 CortexIQ Classifier
Classify
Labels each changed function Logic, Log or No Impact, with a confidence score, reasoning and risk factors.
- 05 CortexIQ Classifier
Assess
Flags the direct callers of every logic change as downstream impact, with risk levels.
- 06 CortexIQ Explainer
Explain
Writes plain-English explanations and an impact report, and answers your questions about the code.
Capabilities
Maps dependencies across PL/I and VB6 code, classifies the impact of every change and explains it in plain English — to speed up modernization and change management.
-
01 Multi-Level Dependency Analysis
Trace file- and function-level dependencies across your codebase in interactive graphs, with call depth, fan-in, fan-out and centrality.
-
02 Intelligent Impact Assessment
See which functions and files a change affects, with risk levels and plain-English explanations, before it ships.
-
03 Context-Aware Change Filtering
Every changed function is classified as Logic, Log or No Impact, so comment, formatting and rename-only edits don't take review time.
-
04 AI Code Assistant
Ask questions about your code, your latest edits and their dependencies, answered from the analysis.
-
05 Legacy-to-Python Conversion
Convert PL/I and VB6 functions to Python, with manual-review flags where the logic needs a closer look.
-
06 Test Automation Migration
Move Coded UI and Cypress test suites to Playwright TypeScript.
-
07 Design Document Sync
Upload a Word design document and get back an updated copy that reflects the code change.
Use cases
-
Change a core banking calculation safely
One procedure's logic has to change, and nobody is sure what else depends on it.
- Map
- Change
- Classify
- Assess
- Explain
Reviewers see which functions and files the change touches, with risk levels, before it ships.
-
Plan a PL/I or VB6 modernization
A legacy estate has to move, but its dependencies were never documented.
- Upload
- Map
- Convert
- Review
Dependency maps ground the plan, and functions convert to Python with flags where logic needs a closer look.
-
Move test automation to Playwright
Coded UI and Cypress suites are holding a team back from a modern test stack.
- Upload
- Map
- Convert
- Download
Suites convert to Playwright TypeScript, file by file, ready to run in your pipeline.
Bring a module or a recent change from your PL/I or VB6 estate. We'll show you its dependency map and which functions the change really affects.
AI agents
Regex parsing finds the structure; the agents add calls, impact and explanations, and every step has a deterministic fallback.
-
CortexIQ Mapper
Traces dependencies
Extracts calls, parameters and entry points for each function, so the dependency graph reflects how the code really runs.
-
CortexIQ Classifier
Judges each change
Decides whether a change is Logic, Log or No Impact, and flags the direct callers of every logic change.
-
CortexIQ Explainer
Explains the impact
Writes the impact report and answers questions about your code, your latest edits and their dependencies.
-
CortexIQ Converter
Modernizes code and tests
Converts PL/I and VB6 functions to Python, and Coded UI and Cypress suites to Playwright TypeScript.
Your code stays yours
-
Self-hosted model
CortexIQ runs on a self-hosted, OpenAI-compatible model endpoint, with no dependency on public AI services.
-
Local embeddings
The search index behind the impact report is built with local embeddings, not a public AI service.
-
Every edit versioned
The original file and its last five versions are kept, so every analysis can be traced back to the code it saw.
-
Deterministic fallbacks
If a model step fails, regex parsing and rule-based classification keep the analysis going.
Integrations
- Legacy languages
- PL/I VB6
- Test frameworks in
- Coded UI SpecFlow Cypress Cucumber
- Outputs
- Python Playwright Word (.docx) HTML reports
- AI models
- Your private model OpenAI-compatible endpoint
- Platform
- Docker
On the roadmap
Part of the CortexIQ architecture and in development.
-
COBOL & Copybook Support (Roadmap)
Dependency and impact analysis for COBOL programs, with copybook resolution.
-
Selective Regression Testing (Roadmap)
Select only the regression tests on a change's impact path.
-
Business-Function Impact (Roadmap)
Map affected code to the business functions it supports, and trace impact through every call level.
-
Dead-Code & Hotspot Detection (Roadmap)
Flag unreachable code and performance hotspots across the estate.
Also see QAI, InsightMesh and AIM
Get started with CortexIQ
Book a demo and we'll map a slice of your PL/I or VB6 estate, classify a real change and show you the report your reviewers would get.