Skip to main content
IBM logo on a building, symbolizing a $40B loss after Anthropic's COBOL translation tool announcement [timesofindia.indiatime

Editorial illustration for IBM's USD 40B loss tied to COBOL translation, not true modernization

AI COBOL Tool Sparks IBM's $40B Market Meltdown

IBM's USD 40B loss tied to COBOL translation, not true modernization

Updated: 3 min read

The market’s reaction was swift and brutal. IBM lost $40 billion in value, and the narrative was simple: the mainframe giant had fumbled the modernization of COBOL. But that story is wrong.

It’s a convenient headline, not the truth. The real problem isn’t translation, it’s the illusion that translation equals transformation. IBM’s watsonx Code Assistant for Z can turn COBOL into Java or Python.

That’s the easy part. The hard part, the part that actually costs money and delivers value, is everything else. Data architecture redesign.

Runtime replacement. Transaction processing integrity. Hardware-accelerated performance.

These are the decades-deep entanglements of software and hardware that no line-by-line conversion can touch. Royal Bank of Canada, ANZ Bank, and the National Organization for Social Insurance have all used IBM’s AI tool to accelerate modernization. But they stayed on IBM Z.

They didn’t leave the mainframe. They didn’t solve the ROI problem. They just translated.

And translation, as IBM’s own communications director admits, is the easy part.

On Tuesday, Anthropic published tools that let Claude read, analyze and translate legacy COBOL into modern languages like Java and Python. By the end of the trading day, investors had wiped roughly $40 billion from IBM's market cap — the company's biggest single-day drop in 25 years — pricing the announcement as an existential threat to IBM's mainframe business.

The market’s $40 billion panic was a reaction, but not a revelation. IBM’s own argument, that COBOL translation is trivial while systems redesign is the real challenge, exposes a deeper truth. Translation alone does not modernize.

It paints old walls with new paint and calls the house rebuilt. What banks and insurers actually need is not a COBOL-to-Java dictionary; it’s a decoupling from the mainframe’s iron grip on their architecture. IBM’s watsonx keeps them on Z.

That’s not liberation. That’s leasing the same cell with a fresh coat of AI polish. The ROI problem remains untouched, buried under decades of hardware dependency.

Investors saw a translation. What they missed was the fortress. And a painted fortress is still a fortress.

Common Questions Answered

How does Anthropic's Claude Code tool potentially impact IBM's mainframe business?

Anthropic claims its Claude Code tool can modernize COBOL software in quarters instead of years, potentially threatening IBM's revenue from mainframe servicing and consulting. The tool can uncover hidden workflows, identify code dependencies, and provide insights for system redesign, which could accelerate the migration of legacy systems away from IBM mainframes.

Why is modernizing COBOL code traditionally challenging?

COBOL modernization is difficult because the code often reflects decades of institutional knowledge and workflows, and is frequently poorly documented. The shrinking pool of COBOL programmers and the complexity of understanding legacy systems make translation and migration a slow and expensive process, with most university computer science programs no longer teaching the language.

What does IBM say is the real challenge in modernizing legacy COBOL systems?

According to an IBM spokesperson, translating COBOL is the easy part. The real work involves complex tasks like data architecture redesign, runtime replacement, maintaining transaction processing integrity, and addressing the decades-old tight coupling between software and hardware. IBM argues that these challenges cannot be simply solved by line-for-line code translation.

LIVE03:21OpenAI's Miles Wang in Talks for USD 2B AI Drug Discovery Startup