Hi,
Some of you saw my transpiler thread here about the transpiler. The tool flags database calls as "manual work required", so I built the tool that picks up where it leaves off.
For shops with COBOL systems hitting DB2, VSAM or IMS, Easy COBOL DB Migrator generates Oracle-ready SQL schemas and a typed data access layer directly from your COBOL source and copybooks.
It handles flat files, all 5 VSAM types (KSDS, ESDS, RRDS, VRRDS, LDS), DB2 embedded SQL with host variable resolution, CICS file operations and IMS/DL-I with segment hierarchy flattening to foreign keys. DAL output in Java, C#, Python, C++, Rust and Go.
Type mapping covers every PIC/USAGE combination. PIC S9(7)V99 COMP-3 becomes NUMBER(9,2) in Oracle. Level 88 conditions become CHECK constraints or BOOLEAN columns. OCCURS arrays normalize to child tables. VSAM RECORD KEY becomes PRIMARY KEY, ALTERNATE KEY becomes an index.
Enterprise edition includes a Data Extractor: reads actual COBOL data files, handles EBCDIC-to-ASCII (CP037), unpacks COMP-3 packed decimals, exports as SQL INSERTs or CSV.
Desktop app, runs offline, source code never leaves your machine.
Free demo at: https://mecanik.dev/en/products/easy-cobol-db-migrator/
Demo is PostgreSQL + C++, up to 3 source files, 1000 lines each.
Screenshots:
Samples (CUSTOMER-FILE.dat + migrate_customer_file.sql): https://drive.google.com/drive/folders/14OKRMP5EjHfqoPfwRwj5YcPC4q5x_mqi?usp=sharing
If you've dealt with Oracle migrations from COBOL/DB2 systems, curious what edge cases you ran into; host variable scoping, cursor handling, anything with REDEFINES over DB2 structures?