Hello there!
I would love to see a parser for Cobol Code. I'm using Windsurf/Codeium for Legacy Application Modernization and it will help a lot our project.
Thanks
COBOL-Related File Extensions Reference
| Extension |
Description |
Context / Environment |
.cob / .cbl |
COBOL source program files |
COBOL compilers (IBM, Micro Focus, GnuCOBOL, etc.) |
.cobol |
COBOL source program (variant) |
Some COBOL environments |
.cpy / .cp |
Copybooks (include files with reusable code/data structures) |
COBOL (all environments) |
.cblle |
COBOL Language Environment source |
IBM z/OS, LE environment |
.lst |
Compilation listing file |
COBOL compilers (IBM, Micro Focus) |
.int |
Intermediate code (pre-compiled) |
Micro Focus COBOL |
.gnt |
Generated object code (runtime ready) |
Micro Focus COBOL |
JCL (Job Control Language)
| Extension |
Description |
Context / Environment |
.jcl |
JCL scripts for batch job execution |
IBM z/OS mainframe |
.job |
Job definition file |
Mainframe batch jobs |
.prc / .proc |
JCL procedure (reusable steps) |
JCL libraries |
.cntl |
Control members (job libraries) |
JCL datasets |
.sysin |
Input parameter/control file |
JCL job input |
VSAM / Data Files
| Extension |
Description |
Context / Environment |
.dat / .data |
Data files |
General COBOL data storage |
.vsam |
VSAM dataset (KSDS, ESDS, RRDS) |
IBM z/OS |
.seq |
Sequential file |
COBOL batch programs |
.idx / .ind |
Index files |
Indexed sequential files |
.rec |
Record files |
Data exchange / COBOL input-output |
CICS (Online Transaction Processing)
| Extension |
Description |
Context / Environment |
.bms |
CICS BMS map set source |
CICS (IBM z/OS) |
.map |
CICS map (compiled BMS screen) |
CICS terminal screens |
.cics |
CICS-related program definitions |
Legacy environments |
.cbl (with EXEC CICS) |
COBOL with embedded CICS commands |
CICS applications |
Utilities / Listings / Outputs
| Extension |
Description |
Context / Environment |
.log |
Execution log file |
Batch/Job output |
.out |
Execution output file |
COBOL or JCL runs |
.lst |
Compilation or job listing |
COBOL / JCL |
.map |
Memory map or address map |
Compiler/linker outputs |
.sym |
Symbol table file |
Debugging / linkage |
Database / Integration
| Extension |
Description |
Context / Environment |
.ddl |
Database definition language (tables, schemas) |
DB2 with COBOL |
.sql |
SQL scripts (embedded or standalone) |
Pre-compiled COBOL/DB2 |
.prn |
Print/output files |
COBOL reports |
.lib |
Library files |
Copybooks / object libraries |
.mac |
Macro source files |
Assembler / COBOL hybrid use |
.ctl |
Control file |
JCL / job execution input |
Notes
- On IBM z/OS mainframes, many files do not have extensions because they are stored in PDS/PDSE datasets (e.g.,
USER.COBOL.SOURCE, USER.COBOL.COPYLIB, USER.JCL).
- In Micro Focus COBOL, ACUCOBOL, and GnuCOBOL, extensions are consistently used in line with modern operating systems.
- Some companies adopt custom conventions, such as
.pco or .inc for copybooks.
https://github.com/yutaro-sakamoto/tree-sitter-cobol
Exafunction
