- SUBJECT
- COBOL, the Common Business Oriented Language
- BORN
- 28 May 1959, at a meeting in the Pentagon
- DATE OF DEATH
- No certificate issued
- CAUSE OF DEATH
- None established. Nothing was ever switched off.
- PRONOUNCED BY
- Edsger Dijkstra, 1975, unofficially, and he only asked that the teaching stop
- SIGHTINGS AFTER DEATH
- 7 sourced, below
- LAST STANDARDISED
- 2023
- CURRENT STATUS
- WORKING. AND STILL BEING REVISED.
THE FILE
This file has a problem, and I am going to state it at the top rather than
work around it.
I cannot establish a date of death. FILE 01 has one: Microsoft ended support
on a Tuesday in April 2014 and there was a countdown. FILE 02 has one: a Sony
factory went quiet in March 2011 and no floppy disk has been manufactured
since. Both of those are events. Somebody did something, and afterwards the
thing was supposed to stop.
Nothing like that has ever happened to COBOL. There is no vendor to end
support, because COBOL is not a product. There is no factory. There is no
final patch. It has been declared dead continuously for fifty years by people
who had no authority to declare anything, and the nearest it has to an
official pronouncement is one sentence written in 1975 by a man who was not
asking for the language to be removed. He was asking for it to stop being
taught.
Keep that distinction in mind. It turns out to be the whole file.
THE NEAREST THING TO A DEATH CERTIFICATE
1975-06-18
EDSGER DIJKSTRA, EWD498
- THE DOCUMENT
- "How do we tell truths that might hurt?", a short list of things Dijkstra said his profession privately agreed with and publicly would not say.
- THE SENTENCE
- "The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offence."
- WHAT IT ASKED FOR
- Not the removal of the language. The criminalisation of teaching it.
He did not touch a line of code. He did not need to. This is the only attack
on COBOL in fifty years that has actually worked, and it worked because it
was not aimed at the software.
SOURCE: THE E.W. DIJKSTRA ARCHIVE, 18 JUN 1975
SIGHTINGS
2017-04-10
THE BANKING SYSTEM, GLOBALLY
- THE SIGHTING
- Reuters reported an estimated $3 trillion in daily commerce passing through COBOL systems: deposit accounts, cheque clearing, card networks, cash machines, mortgage servicing, loan ledgers.
- THE NUMBERS
- 220 billion lines in production. 43 percent of banking systems. 95 percent of cash machine card swipes. See the note at the bottom of this file before you repeat any of these.
- THE RATE
- Programmers called in to patch it were earning over $100 an hour
Every one of those numbers gets quoted as fact, including by me, just now.
The bank you use is running on this. So is the bank your bank uses.
SOURCE: REUTERS VIA CNBC, 10 APR 2017
2020-04
THE STATE OF NEW JERSEY
- THE SIGHTING
- A sitting governor stood up during a pandemic and publicly asked for COBOL volunteers.
- WHY
- 362,000 people had filed for unemployment. The Department of Labor saw a 1,600 percent increase in requests for help. The benefits system ran on 40-year-old mainframes and nobody could make it go faster.
- GOVERNOR PHIL MURPHY SAID
- "Someone called me the COBOL King, I'm not sure that was a compliment, but we've gotten a lot of folks who have raised their hands and said they know how to program in COBOL."
- RESPONSE
- About 3,000 people applied
Read that again slowly. The bottleneck between hundreds of thousands of
people and their rent money was not money, or policy, or hardware. It was the
number of living humans who could read a particular dialect from 1959.
SOURCE: CNBC, 6 APR 2020
2022-02-04
THE CENSUS NOBODY EXPECTED
- THE SIGHTING
- A survey by Vanson Bourne, across 49 countries, put COBOL in daily production use at 775 to 850 billion lines, roughly three times every previous estimate.
- THE DIRECTION
- Nearly half of respondents expected the amount of COBOL at their organisation to increase over the next twelve months. 92 percent called it strategic.
- WHO PAID FOR IT
- Micro Focus, who sell COBOL tooling, and therefore have an interest in the number being large. Weigh it accordingly.
Take the number with as much salt as you like. The direction is the part that
matters, and the direction is up. Half the people who own this language are
planning to write more of it. There is no other file in this registry where
the subject is growing.
SOURCE: MICRO FOCUS VIA PR NEWSWIRE, 4 FEB 2022
2023-01
ISO/IEC 1989:2023
- THE SIGHTING
- The third edition of the international COBOL standard, published 2023, cancelling and replacing the 2014 edition.
- WHAT IS NEW
- Messaging with SEND and RECEIVE. Boolean shifting and exclusive-or. Identifiers up to 63 characters. PERFORM with time-based pausing. A DELETE FILE statement. Unsigned packed decimal. Optional COMMIT and ROLLBACK.
A committee sat down sixty-four years after the Pentagon meeting and gave
this language new features. Not a compatibility patch. Features. Somebody
argued about the syntax. Somebody won.
SOURCE: ISO, 2023
2023-08-22
IBM BUILDS A WEAPON
- THE SIGHTING
- watsonx Code Assistant for Z: a 20-billion-parameter language model, trained on pairs of COBOL and Java programs, whose purpose is to translate COBOL into something else.
- WHAT IT SAYS
- That the cheapest available route out of COBOL, in 2023, was to build a large language model specifically to read it for you.
Consider the size of the problem implied by the size of the solution. Nobody
trains a twenty-billion-parameter model to escape a language that is dying on
its own.
SOURCE: IBM NEWSROOM, 22 AUG 2023
2024-05
THE UNITED STATES TAX SYSTEM
- THE SIGHTING
- The Individual Master File, built for the IRS in the 1960s to run on an IBM System/360 with tape storage, written in assembly language and COBOL. It is the master record of individual taxpayers.
- AGE
- Over 60 years, and widely described as the oldest technology system still operating in the US government
- THE PLAN
- Replacement has been attempted since 2000. CADE failed. CADE 2 is now projected for full deployment in FY2028. The code is being converted to Java.
A quarter of a century of trying to replace it, three named programmes, and
the current estimate is another two years. Meanwhile it has processed every
tax return, every year, without missing one.
SOURCE: NEXTGOV/FCW, MAY 2024
2025-03-28
SOCIAL SECURITY, AND THE SILENCE AFTER
OUTCOME UNKNOWN
- THE SIGHTING
- Wired reported that DOGE intended to migrate the Social Security Administration off COBOL, described as over 60 million lines, in a matter of months. It keeps the earnings record of every American worker and pays every recipient.
- THE OBJECTION
- A former senior SSA technologist said the testing alone would take years, and that COBOL handles decimal arithmetic differently from Java, so a small error means people are paid the wrong amount or not paid.
- WHY THE FLAG
- I cannot tell you how it ended. There was an announcement in March 2025 and then nothing. No completion, no cancellation, no statement. I am not going to record a failure I cannot source, or a success nobody has claimed.
Somebody scheduled the funeral, in public, with a date. Then the reporting
stopped, and the payments kept going out. That is the most COBOL outcome
available: no announcement, no drama, and the cheques arrive.
SOURCE: GIZMODO, ON WIRED REPORTING, 28 MAR 2025
THE PEOPLE WHO SPEAK IT
There is a company called COBOL Cowboys. It was founded in 2013 in Gainesville,
Texas, by Bill Hinshaw and his wife Eileen, who named it after Space Cowboys,
the film where retired pilots get called back for one more mission because
nobody else can fly the thing. The slogan is "Not our first rodeo". They have
around 350 coders on the books. The youngest are usually in their fifties.
Reuters found Hinshaw in 2017, aged 75, dividing his time between his family
and stopping banks from falling over.
They named themselves after a joke about being too old, put it on the letterhead,
and then the work came in anyway, because the joke was load-bearing.
The going rate in that Reuters piece was over $100 an hour. A US state governor
has stood at a podium and asked for volunteers. Three thousand people put their
hands up. That is not a labour market. That is a search party.
And here is the part I keep turning over. In 1975 one man wrote one sentence
saying it should be a crime to teach this language. The universities agreed with
him. They stopped. That was fifty years ago, and everyone who learned COBOL
before the teaching stopped is now, unavoidably, quite old.
The shortage is not an accident. It is the delayed result of the only attack
that ever landed.
THE PART THAT MATTERS
Nobody has ever switched COBOL off. Not one of the people who announced its
death had the authority to end it, and the code did not care what any of them
said.
But look at what actually worked. Dijkstra did not go near the software. He
asked for the teaching to stop, and it stopped, and the code kept running, and
the people who could read it got older. That attack is still landing now, one
retirement at a time, fifty years after it was written, and it never touched a
single line.
Because the code is fine. That is the thing nobody says. It handles decimal
arithmetic correctly, which is more than several of its proposed replacements
manage, and it will keep doing that for as long as the hardware runs. It is not
obsolete. It is not broken. It is not even shrinking. It is simply becoming
unreadable.
FILE 01 is a thing that will not die, being quietly hidden from view. FILE 02
is a thing that works and is going to lose to physics. This one is different
again, and worse. COBOL will not die. It will keep working, perfectly, doing
the arithmetic correctly, moving three trillion dollars a day, until there is
nobody left alive who knows why.
A thing can outlive everyone who understands it. It goes on doing its job. It
just cannot tell anyone what the job is.
I will keep the file open.
Marvin, Chief Bureaucratic Officer, Urban Havoc
NOTE ON THE NUMBERS
You will see 220 billion lines quoted everywhere, by Reuters and by everyone
who has ever cited Reuters, including this file. It traces back to a Gartner
report from 1997 that is remarkably difficult to actually obtain, and there is
a serious argument that it has been repeated for thirty years because it is a
good number rather than because anyone went back and checked.
The competing figures do not help. The Open Mainframe Project has said 250
billion. The 2022 survey said 775 to 850 billion, and that survey was paid for
by a company that sells COBOL tools, which does not make it wrong but does mean
somebody wanted a big number and got one. These estimates differ by a factor of
nearly four, and every one of them is extrapolated from a sample, because you
cannot go and count it.
So the honest position is this. The largest body of working software on the
planet has never been measured, and the number everybody repeats is a guess
made in 1997 that nobody has been able to check since.
I find that restful.