Mainframe & Legacy Enterprise Languages — Tier 3 Index
Mainframe & Legacy Enterprise Languages — Tier 3 Index
- Type: Family index (encyclopedic)
- Family: Mainframe and legacy enterprise languages beyond COBOL/Fortran
- Languages catalogued: ~20 mainframe/midrange/legacy-enterprise languages
- Last updated: 2026-05-07
Family overview
This index covers the languages that run the world’s banks, insurers, airlines, governments, and enterprise resource planning systems — the code that processes a majority of credit card transactions, payroll runs, and ERP transactions on any given business day. These languages share a generational arc: most were designed between 1957 and 1985 for IBM mainframes, AS/400 midrange systems, or specific business niches (SAP for ABAP, Software AG for Natural). They are not glamorous, but they are durable; almost every entry in this table is still running production workloads in 2026, and several are actively developed. The defining property of this family is that the code outlives the systems — programs written in 1985 are routinely still in production, often migrated forward through three or four hardware generations without source-level rewrites.
In our deep library
- cobol — the canonical mainframe business language; covers COBOL-85, Enterprise COBOL, the IBM zSystems story, and modernization paths
- fortran — scientific/engineering legacy lineage; modern Fortran is alive in HPC
- ada — defense/safety-critical; covers Ada-83, Ada-95, Ada 2012, SPARK
Tier 3 — the family
| Language | First release | Status (2026) | Niche / use case | Why it matters | Source URL |
|---|---|---|---|---|---|
| PL/I | 1964 | Active maintenance; declining new dev | IBM general-purpose mainframe language; banking, insurance | Designed to unify FORTRAN, COBOL, and ALGOL; still in production at major insurers; IBM Enterprise PL/I for z/OS still receives compiler updates | https://www.ibm.com/products/pli-compiler-zos |
| JCL (Job Control Language) | 1964 | Active; mandatory on z/OS | z/OS batch job specification language | Every z/OS batch job is described in JCL; not Turing-complete but essential. Modern alternatives (z/OSMF workflows) exist but JCL persists | https://www.ibm.com/docs/en/zos/3.1.0?topic=zos-jcl |
| RPG II / III / IV / Free-Form RPG | 1959 (RPG); RPG IV 1994; Free-Form 2014 | Active development; IBM i platform | IBM i (AS/400) business apps; report generation, transaction processing | Free-Form RPG (introduced 2014, expanded since) modernized RPG to look like a contemporary structured language; active customer base at thousands of mid-size businesses | https://www.ibm.com/docs/en/i/7.5?topic=programming-rpg |
| CL (Control Language) | 1978 | Active; IBM i scripting | IBM i system scripting and command-language | The shell scripting equivalent for IBM i; every IBM i admin writes CL | https://www.ibm.com/docs/en/i/7.5?topic=concepts-control-language |
| REXX | 1979 | Active | IBM’s general-purpose scripting language; cross-platform | Default scripting on z/OS, z/VM, OS/2; still ships with z/OS in 2026; Open Object Rexx is the OSS implementation | https://www.ibm.com/docs/en/zos/3.1.0?topic=zos-rexx |
| NetREXX | 1996 | Open-sourced 2011; Apache project | REXX syntax targeting the JVM; bridges REXX programmers to Java | Created by Mike Cowlishaw (REXX’s original author); allows REXX scripts to use Java libraries | https://netrexx.org/ |
| Object REXX / ooRexx | 1997 (IBM); ooRexx 2005 (open source) | Active community | OO extension of REXX; cross-platform | Open Object Rexx (ooRexx) is the OSS continuation after IBM withdrew its commercial product; Windows/Linux/macOS | https://www.oorexx.org/ |
| Easytrieve / Easytrieve Plus | 1969 | Maintenance; CA/Broadcom | z/OS report writing and data extraction | Used at insurers and banks for ad-hoc reporting against VSAM/DB2; Broadcom still sells it | https://techdocs.broadcom.com/us/en/ca-mainframe-software/management/ca-easytrieve-report-generator.html |
| Natural | 1979 | Active; Software AG | Mainframe ADABAS frontend; insurance and banking | Tightly coupled to ADABAS; large install base in Europe especially. Software AG was acquired by IBM/Silver Lake in 2024 — long-term roadmap uncertain | https://www.softwareag.com/en_corporate/platform/adabas-natural.html |
| ABAP | 1983 | Active development; ABAP Cloud since 2023 | SAP ERP business logic; the language of S/4HANA | The world’s largest business-software install base runs ABAP. ABAP Cloud (released 2023, default for new dev 2025+) is the modernization path. ABAP RAP (RESTful Application Programming Model) is the contemporary style | https://help.sap.com/docs/abap-cloud |
| Progress 4GL / OpenEdge ABL | 1984 | Active; commercial | Progress Software’s integrated database+language; legacy ERP systems | Many distribution, manufacturing, and healthcare ERPs run on OpenEdge; Progress still actively releases | https://www.progress.com/openedge |
| Informix 4GL | 1986 | Maintenance; IBM | Database-coupled 4GL; Latin American and Asian government systems | IBM acquired Informix in 2001; 4GL still supported but Genero (FourJs) is the modern fork most customers migrate to | https://www.ibm.com/docs/en/informix-servers/14.10 |
| Genero (FourJs) | 2001 | Active; commercial | Modern OpenSource-feel fork of Informix 4GL with mobile/web targets | Where Informix 4GL customers go when they want a contemporary IDE and mobile delivery without rewriting | https://www.4js.com/ |
| FoxPro / Visual FoxPro (VFP) | 1984 (FoxBASE) / 1995 (VFP) | Archived; Microsoft sunset 2015 | xBase database language with integrated DB engine | Microsoft acquired Fox Software in 1992; VFP 9 was the last release. VFPX is a community group keeping it usable | https://github.com/VFPX |
| dBase / dBase III/IV/V | 1979 / 1984 / 1988 / 1994 | Niche; dBase LLC sells modern editions | Original PC database language; “xBase” tradition | Defined the entire xBase family; the .DBF file format is still everywhere (GIS shapefiles, legacy data exchange) | https://www.dbase.com/ |
| Clipper | 1985 | Archived; superseded by Harbour | xBase compiler that produced standalone .EXE files (no runtime) | Massive late-80s/90s install base for DOS business apps; Computer Associates abandoned it in 1999 | https://en.wikipedia.org/wiki/Clipper_(programming_language) |
| Harbour | 1999 | Active; OSS | Open-source Clipper-compatible compiler; cross-platform | The Clipper community’s continuation path; compiles classic Clipper code on modern Windows/Linux/macOS | https://harbour.github.io/ |
| ALGOL 60 | 1960 | Historical; near-zero production | Academic algorithm description; ancestor to Pascal, C, modern langs | The grammar of ALGOL 60 (BNF) defined how we describe languages; ancestor of essentially every block-structured language | https://en.wikipedia.org/wiki/ALGOL_60 |
| ALGOL 68 | 1968 | Historical; few maintained implementations | Academic; influenced C and Ada | Famously over-designed but introduced concepts (orthogonality, user-defined types) that took decades to land in mainstream langs | https://algol68.sourceforge.io/ |
| Simula 67 | 1967 | Historical | First object-oriented language; classes, inheritance, coroutines | Direct ancestor of C++ (Stroustrup explicitly cites it); coroutines were Simula features 50 years before they reached Python/Kotlin | https://en.wikipedia.org/wiki/Simula |
| HAL/S | 1972 | Maintenance; NASA legacy | Space Shuttle onboard guidance/navigation/control software | Designed by Intermetrics for the Shuttle; flew every Shuttle mission. Successor systems use Ada and C++ but HAL/S is preserved for STS heritage code | https://history.nasa.gov/computers/Ch4-5.html |
| JOVIAL (J73 etc.) | 1959 | Maintenance; defense | US military aviation embedded systems (B-52, B-1, F-15, F-16, AWACS) | The DoD’s pre-Ada standard; thousands of avionics systems still depend on JOVIAL code. USAF officially supports it | https://www.dote.osd.mil/ |
| Forth (Open Firmware on legacy Sun/PowerPC/SPARC) | 1970 (Forth); 1994 (Open Firmware) | Maintenance; Sun/Oracle SPARC, IBM POWER, Apple PowerPC era | Stack-based bootloader / firmware language; IEEE 1275 | The boot prompt on Sun, IBM RS/6000, and pre-Intel Macs was Open Firmware Forth; still in IBM POWER systems | https://www.openfirmware.info/ |
| MUMPS / M | 1966 | Active; healthcare | Healthcare records (Epic, MEDITECH, VA VistA), brokerage back-offices | An estimated majority of US health-records data lives in MUMPS systems; InterSystems IRIS (formerly Caché) is the modern descendant | https://www.intersystems.com/products/intersystems-iris/ |
| GAP (Global Application Platform) / SBL / SAS | 1976 (SAS) | Active; SAS Institute | Statistical/analytics 4GL; financial regulatory reporting | SAS is the regulatory-reporting language for many central banks; SAS Viya is the modern cloud platform | https://www.sas.com/ |
Notable threads
Mainframe languages don’t die — they migrate. The conventional Silicon Valley narrative (“nobody uses COBOL anymore”) consistently misreads what’s actually happening. IBM Z systems shipped record revenue in 2024-2025; banks aren’t running COBOL because they can’t migrate but because the cost-benefit math says don’t. The same is true for PL/I, RPG, REXX, Natural, and ABAP — these languages are economically rational for their workloads. The 2020 COVID-era unemployment-claims surge that famously broke several US state unemployment systems wasn’t a COBOL failure; it was a capacity-planning failure that affected systems written in COBOL, Java, and .NET equally. The actual modernization story in 2026 is “wrap, don’t rewrite”: expose mainframe transactions as REST/GraphQL APIs (IBM z/OS Connect, Software AG webMethods) and write new functionality in Java/Node alongside the legacy core.
The xBase diaspora. The xBase family — dBase → FoxPro → Clipper → Harbour, plus countless commercial variants — once ran a meaningful fraction of small-business computing. Microsoft’s discontinuation of Visual FoxPro in 2015 was the end of the commercial xBase era, but the open-source Harbour project is keeping classic Clipper code compiling on modern OSes, and the .DBF file format is everywhere (GIS shapefiles still use it as their attribute table format). xBase patterns — the tightly-coupled IDE+language+DB integration — also influenced PowerBuilder, Delphi, and arguably Microsoft Access.
ABAP’s two-track future. SAP’s ABAP situation is the most interesting in the family because it’s actively splitting into two worlds. “Classic” ABAP (running in on-premise SAP NetWeaver / S/4HANA on-premise) continues with all its historical baggage — direct database access, dynamic SQL, OPEN SQL extensions. “ABAP Cloud” (mandatory for new dev in S/4HANA Cloud Public Edition since 2023) is a sandboxed, released-API-only subset designed to be cloud-safe and upgrade-stable. SAP’s BTP (Business Technology Platform) also lets developers write ABAP in the cloud against Steampunk runtime. Existing customers face a multi-year migration to “clean core” ABAP that is the closest analog in the family to the COBOL → Java story.
The ALGOL family tree. Although ALGOL itself is essentially gone from production, its descendants run everything. The line ALGOL 60 → CPL → BCPL → B → C → C++/Java/C#/Go/Rust connects ALGOL to most contemporary mainstream languages. ALGOL 60 → Simula 67 → C++ → modern OO is another path. ALGOL 60 → Pascal → Modula-2 → Oberon → Go is yet another. The reason ALGOL never became dominant — committee design, no I/O standardization, slow compilers — became less relevant once it had spawned descendants.
Simula is older than you think. Simula 67 had classes, inheritance, virtual methods, garbage collection, and coroutines a decade before Smalltalk-80 and two decades before C++. Bjarne Stroustrup encountered Simula at Cambridge in the 1970s and explicitly designed C++ (“C with Classes”) to bring Simula’s OO into a systems-programming setting. Most of the OO concepts the industry rediscovered through C++/Java/C# in the 1990s were Simula features in 1967.
Citations
- IBM, “z/OS Enterprise PL/I documentation” (2024)
- IBM, “RPG and ILE programming guide for IBM i 7.5” (2024)
- IBM, “TSO/E REXX User’s Guide” (2024)
- Software AG (now IBM), “ADABAS & Natural product roadmap” (2024)
- SAP, “ABAP Cloud development model — Cloud-first ABAP” (help.sap.com, 2023-2025)
- SAP, “ABAP RESTful Application Programming Model (RAP)” documentation
- Progress Software, “OpenEdge ABL Language Reference” (2024)
- IBM, “Informix 4GL documentation set” (2024)
- Broadcom, “Easytrieve Report Generator user guide” (2024)
- Computer History Museum, “Simula 67 oral histories with Ole-Johan Dahl and Kristen Nygaard”
- NASA History Office, “Computers in Spaceflight: The NASA Experience” — HAL/S chapter
- US DoD, “JOVIAL Programming Language” reference (DoD STD-1589C, 1984)
- InterSystems, “Caché/IRIS technology heritage from MUMPS” (2024)
- Stroustrup, B. “The Design and Evolution of C++” (1994) — Simula influence chapters
- Cowlishaw, M. “The REXX Language: A Practical Approach to Programming” (1990)
- IBM zSystems quarterly revenue disclosures, IBM 10-Q filings 2024-2025