Why COBOL? Real History & Why It's Still Running Today
COBOL Fundamentals
Chapter 1 · Why COBOL? Real History & Why It's Still Running Today
COBOL stands for Common Business-Oriented Language — a name that describes its entire real design philosophy in three words. It was never meant to be a general-purpose language for every kind of programming; it was built, deliberately, for one specific real purpose: processing business data at scale, in a form readable enough that a manager, not just a programmer, could follow the logic.
The Real 1959 CODASYL Committee
COBOL's design began in 1959, driven by the CODASYL committee (Committee on Data Systems Languages) — a real, deliberate effort to create one standard business language that could run on machines from competing manufacturers, rather than locking a business into one vendor's own proprietary language. A six-person subcommittee did most of the real design work:
William Selden & Gertrude Tierney
IBM
Howard Bromberg & Howard Discount
RCA
Vernon Reeves & Jean E. Sammet
Sylvania Electric Products
Three competing manufacturers, working together on one shared standard — a genuinely unusual real arrangement for the era, and a direct, deliberate answer to the "vendor lock-in" problem business computing faced at the time.
Two Real, Different Influences
COBOL wasn't invented from nothing — it deliberately combined ideas from two existing real languages. FLOW-MATIC, on which Grace Hopper served as technical adviser, contributed long, readable variable names, English-word commands, and the real, foundational idea of separating data descriptions from instructions — exactly the split that would later become COBOL's own DATA DIVISION and PROCEDURE DIVISION. COMTRAN contributed real arithmetic formula support, an improved IF statement, and — directly relevant to Chapter 3 of this course — the PICTURE clause itself.
COBOL 60: A Real, Specific Date
The finished specification was approved by the executive committee on 8 January 1960, then sent to the US Government Printing Office, which published it as COBOL 60 — the real, original standard every later COBOL revision built on.
Even this simplest possible real COBOL program already shows the shape Chapter 2 covers in full — four named divisions, appearing in a fixed order, each with a distinct real job.
Why This Matters Today, Not Just Historically
COBOL's real, continued relevance is genuinely striking. A 1997 estimate put roughly 200 billion lines of COBOL in active existence, running an estimated 80% of all business programs at the time. More recently, a real 2020 statistic found that COBOL processed 95% of the time a credit or debit card was swiped. Banking, insurance, and major government agencies — including the IRS, the US Treasury, and the VA — still run real, live COBOL systems today.
Hands-On Exercises
Using this chapter's own real material, explain in your own words why crediting Grace Hopper as "the creator of COBOL" is inaccurate, and what her real, documented role actually was.
📄 View solutionUsing this chapter's own real material on FLOW-MATIC and COMTRAN, explain in your own words which specific real COBOL feature traces to which of the two influences, and why.
📄 View solutionA friend asks why anyone would still bother learning a language designed in 1959. Using this chapter's own real, current-relevance statistics, write an accurate answer, in your own words.
📄 View solutionChapter 1 Quick Reference
- COBOL = Common Business-Oriented Language; design began 1959 via the CODASYL committee
- Six real designers: Selden & Tierney (IBM), Bromberg & Discount (RCA), Reeves & Sammet (Sylvania)
- Two real influences: FLOW-MATIC (readable syntax, data/instruction separation) and COMTRAN (formulas, the PICTURE clause)
- Real myth correction: Grace Hopper advised on FLOW-MATIC but, per Jean Sammet's own words, was not COBOL's creator
- COBOL 60 — approved 8 January 1960
- Real current relevance: ~200 billion lines (1997 estimate), 80% of business programs, 95% of card swipes processed by COBOL (2020)