Three languages, one analysis surface.
Most estates are not written in one language. Cobra reads COBOL, PL/I and IBM High-Level Assembler through a single Dictionary MCP surface — and folds JCL, CICS/BMS, IMS/DB and MQSeries into the same picture — so impact analysis crosses language boundaries instead of stopping at them.
COBOL, PL/I and assembler as first-class citizens.
Not a COBOL tool with adapters bolted on. Three core languages on one metadata surface, each analysed in its own right and joined into a single cross-language call graph.
COBOL
PL/I
IBM High-Level Assembler (HLASM)
One distinction worth being precise about: execution today is COBOL-only — the managed runtime runs COBOL. PL/I and assembler are first-class in the analysis surface (the Dictionary MCP), where they are read, mapped and joined into the cross-language call graph.
Complete coverage — and it tells you what it inferred.
Assembler is where migrations stall, because “nobody understands the assembler.” Cobra maps it in full — 100% coverage by construction: every module is faithfully parsed or expanded, and every fact is tagged with its provenance, so an engineer can tell parsed data from inferred data rather than trusting a black box. The component that resolves the hardest macros runs at build time only; nothing third-party ships in the delivered software, which keeps all distributed code free of GPL obligations — a point that matters as much to acquirer due-diligence as it does to regulated-customer procurement.
The rest of the estate, in scope.
The core languages sit alongside the mainframe technologies that bind them together — analysed on the same surface, not treated as someone else’s problem.
JCL
CICS / BMS
IMS / DB
MQSeries
Bring a mixed-language estate.
We will show how the platform reads COBOL, PL/I and assembler together, and where the cross-language dependencies actually are.