cobol-py 0.1.0

COBOL parser for Python, porting the proleap-cobol-parser preprocessor + Cobol.g4 pipeline to a startRule AST

cobol-py

A COBOL parser for Python that ports the parsing pipeline of proleap-cobol-parser (Java) to Python, built on ANTLR4.

cobol-py reproduces proleap's two-stage design:

1. Preprocessor (CobolPreprocessor.g4) — a fixed-format line model plus a document walker that expands COPY copybooks, applies REPLACE pseudo-text, and extracts EXEC CICS / EXEC SQL / EXEC SQLIMS blocks into tagged lines.
2. Main grammar (Cobol.g4) — parses the preprocessed text into a startRule AST.

The deliverable is the full pipeline: raw source → preprocessed text → AST → ASG (Abstract Semantic Graph). The ASG is a typed, registry-backed object model of the program — divisions, sections, data descriptions, paragraphs, statements, and resolved calls — built on top of the startRule AST.

Install

pip install cobol-py             # from PyPI

Or with uv for development:

uv sync                          # create .venv and install antlr4-python3-runtime + pytest
uv pip install -e .              # or, install the package into another project

Runtime dependency: antlr4-python3-runtime 4.13.2.

Quick start

from cobol_py import CobolParserRunner, CobolParserParams, CobolSourceFormatEnum

src = open("examples/example.cbl").read()

# A source format is required — it drives the fixed-format line model.
params = CobolParserParams(format=CobolSourceFormatEnum.FIXED)

ast = CobolParserRunner().parse(src, params)
print(ast.toStringTree(recog=ast.parser))   # noqa: the generated StartRuleContext

Or parse straight from a file (the file's directory becomes the default copybook search path):

from cobol_py import CobolParserRunner, CobolSourceFormatEnum

ast = CobolParserRunner().parse_file(
    "examples/example.cbl", CobolSourceFormatEnum.FIXED
)

Source formats

COBOL source is column-oriented. CobolSourceFormatEnum selects the layout the line reader expects:

Format	Sequence (cols)	Indicator	Area A	Area B
FIXED	1–6	7	8–12	13–72
VARIABLE	1–6	7	8–12	8–end
TANDEM	—	1	2–5	2–end

FIXED is the standard ANSI / IBM reference. Unlike FIXED, VARIABLE does not drop a comment area past column 72, so long AREA B content survives intact.

Preprocessor constructs

CobolPreprocessorImpl performs the textual transforms that a pure grammar cannot:

• COPY — inlines a copybook resolved against params.copy_book_directories / copy_book_files (by cobol-word, literal, or filename).
• REPLACE ==a== BY ==b== — applies pseudo-text replacement to the surrounding source.
• EXEC SQL|CICS|SQLIMS … END-EXEC — tags each line (*>EXECSQL, …) and emits a } terminator so the main grammar's lexer can recognise the block.

from cobol_py import CobolPreprocessorImpl, CobolParserParams, CobolSourceFormatEnum

params = CobolParserParams(format=CobolSourceFormatEnum.FIXED)
preprocessed = CobolPreprocessorImpl().process(src, params)

Walk the AST

The generated listener / visitor let you traverse the startRule tree:

from cobol_py import CobolListener

class MyListener(CobolListener):
    def enterMoveStatement(self, ctx):        # noqa: N802
        print("found MOVE:", ctx.getText())

ASG (semantic layer)

CobolParserRunner().analyze(...) runs the preprocessor + AST parse, then the ASG visitor passes, and returns a typed Program model — the same shape as proleap's ASG, ported to idiomatic Python (snake_case attrs, one class per Java interface+Impl pair, direct attributes instead of getters).

from cobol_py import CobolParserRunner, CobolParserParams, CobolSourceFormatEnum

params = CobolParserParams(format=CobolSourceFormatEnum.FIXED)
program = CobolParserRunner().analyze(src, params)

# Procedure-division statements, fully typed.
proc = program.compilation_unit.program_unit.procedure_division
for stmt in proc.root_paragraphs[0].statements:
    print(type(stmt).__name__, stmt.statement_type)

Coverage (mirrors proleap's metamodel):

• Structure — CompilationUnit / ProgramUnit / four divisions; identification, environment (FILE-CONTROL SELECTs), data (working-storage / linkage / local-storage / file-section FDs with the 01-level hierarchy), procedure (sections / paragraphs / root-paragraphs).
• Statements — all 50 verbs produce a typed node. File I/O (OPEN/CLOSE/ READ/WRITE/REWRITE/DELETE/START), arithmetic (ADD/SUBTRACT/MULTIPLY/DIVIDE/ COMPUTE), control (IF/PERFORM/EVALUATE/GO TO/SEARCH), MOVE/CALL/SET/STRING/ UNSTRING/INSPECT/INITIALIZE/DISPLAY/ACCEPT/STOP, and the C2 tail (SORT/MERGE/ ALTER/CANCEL/RETURN/RELEASE + EXEC CICS/SQL/SQLIMS and the rarer verbs).
• Phrase scopes — every statement-owning phrase (AT END, INVALID KEY, ON SIZE ERROR, ON EXCEPTION, ON OVERFLOW, AT END-OF-PAGE, IF THEN/ELSE, PERFORM inline body, SEARCH/EVALUATE WHEN) owns its nested statements, so they nest under their parent instead of leaking to the paragraph — matching proleap, where these phrases implement Scope.
• Calls — references resolve to ProcedureCall / SectionCall / DataDescriptionEntryCall / FileControlEntryCall (with back-links on the declarations); unresolved names fall back to UndefinedCall.

Clause detail still deferred on a few verbs (full arithmetic/condition operand decomposition, OCCURS/REDEFINES/VALUE/USAGE data clauses, SEARCH/EVALUATE WHEN condition decomposition); every verb already produces its typed node.

Testing

uv run pytest                      # full suite (~197 tests)
COBOL_PY_NIST_FULL=1 uv run pytest tests/test_nist.py   # full NIST suite (slow)

Module	What it checks
tests/test_phase1_leaf.py	leaf types, params, format enum
tests/test_phase2_line.py	line sub-pipeline (reader / indicator / writer)
tests/test_parse.py	full pipeline on small FIXED/TANDEM/VARIABLE fixtures
tests/test_ast_tree.py	parse-tree golden comparison vs proleap's .cbl.tree files
tests/test_nist.py	NIST COBOL-85 conformance (a stride by default; full is opt-in)
tests/test_asg/*.py	ASG layer: foundation, data/procedure structure, statements, file verbs, call resolution, phrase-scope nesting

tests/test_ast_tree.py is the strongest fidelity check: it parses every program under testdata/io/proleap/cobol/ast and asserts the cleaned toStringTree output matches proleap's committed .cbl.tree golden byte-for-byte.

tests/test_nist.py mirrors proleap's gov/nist/*Test.java — it runs each NIST program through parse_file(file, FIXED) and asserts a clean parse. The Python ANTLR runtime simulates the ATN in pure Python, so prediction on this grammar is ~2-4 s per medium NIST file (vs. milliseconds on the JVM); the full 459-file suite is therefore opt-in via COBOL_PY_NIST_FULL=1, while a representative stride runs in the default suite.

Regenerate the parser

The generated modules under src/cobol_py/ are committed, but you can regenerate them from Cobol.g4 / CobolPreprocessor.g4 after editing a grammar:

uv run python scripts/generate_parser.py
uv run pytest                 # verify

The generator drives the official ANTLR4 jar through java. The jar version is derived from the installed antlr4-python3-runtime (so the emitted ATN and the runtime always agree); the jar is cached under .tools/ and downloaded automatically if missing. A JDK must be on PATH.

Project layout

Cobol.g4                       # main COBOL grammar (source of truth)
CobolPreprocessor.g4           # preprocessor grammar (COPY/REPLACE/EXEC/opts)
pyproject.toml                 # uv / hatchling package definition
scripts/generate_parser.py     # regenerate src/cobol_py/*.py from the grammars
src/cobol_py/                  # importable package
  preprocessor/                # line reader/writer, indicator processor,
                               # comment marker, document parser, copybook finders
  asg/                         # Abstract Semantic Graph: typed program model
                               # (divisions, statements, calls) over the AST
  runner.py                    # CobolParserRunner — the public entry point
  Cobol{Lexer,Parser,Listener,Visitor}.py
  CobolPreprocessor{Lexer,Parser,Listener,Visitor}.py
tests/
  fixtures/                    # .cbl/.CPY programs: FIXED/TANDEM/VARIABLE +
                               # COPY + REPLACE + EXEC SQL/CICS
  test_phase1_leaf.py          # leaf types & utils
  test_phase2_line.py          # line sub-pipeline
  test_parse.py                # full-pipeline integration tests
examples/example.cbl           # self-contained FIXED example

Design notes & limitations

• The proleap whitespace model is preserved: NEWLINE and whitespace live on the HIDDEN channel and statements terminate on DOT_FS.
• EXEC CICS/SQL/SQLIMS bodies are parsed inline as a free-form token run up to END-EXEC, gated by the preprocessor-inserted *>EXEC* tags and the } terminator.
• compilerOptions is recognised tolerantly (the option stream is captured up to IDENTIFICATION).
• Parse speed: the runner uses ANTLR's SLL→LL two-stage strategy. SLL is exact and fast for most input; when it bails (ambiguity or a real syntax error), the runner falls back to full LL with the error listeners re-armed, so the parse tree and error behaviour are identical to a plain LL parse. This is a Python-specific optimisation — proleap on the JVM does not need it.
• The ASG is a port of proleap's semantic layer (idiomatic Python: one class per Java interface+Impl pair, snake_case, direct attrs). A handful of clause details are still deferred (see the ASG section above); the parsing pipeline is complete and every verb already produces its typed ASG node.

License

MIT.