Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Meet Cobol's hard core fans

Robert L. Mitchell | Aug. 22, 2014
These folks won't migrate. The reason probably isn't what you're thinking.

Streamlining mainframe applications
Even some of the biggest mainframe shops are streamlining mainframe operations for non-core functions. BNY Mellon runs nine IBM System z10s that supply a total of 54,000 MIPS of compute power and handle $1.5 trillion in transaction processing workloads each day. The Cobol codebase that powers those systems has grown from 343 million lines two years ago to 357 million lines today, adding 2,500 new programs along the way.

"I believe it gives us a competitive advantage, especially with the transaction volumes we're doing," says David Brown, managing director and chief application architect.

But the growth of BNY Mellon's Cobol codebase reflects enhancements to the bank's core transaction processing systems. Few organizations, BNY included, are building entirely new applications in Cobol anymore.

In other areas, BNY Mellon has also been steadily peeling away mainframe applications that aren't strategic to its banking operations. It has moved to packaged applications in some cases, recast some applications in need of a heavy rewrite onto distributed computing platforms and pushed ad-hoc reporting capabilities off the mainframe as well.

I believe [Cobol] gives us a competitive advantage, especially with the transaction volumes we're doing. David Brown, managing director and chief application architect, BNY Mellon

"If you're doing sequential processing and you have a mainframe footprint, that's where that functionality belongs," says Brown. "But on things you're doing ad-hoc -- mobile, big data -- all of those run better on distributed platforms."

When applications that used to be hosted on the mainframe are re-hosted or rewritten to run on distributed computing platforms, however, that makes things more complex when it comes to accessing data that still resides back on the mainframe, Brown says.

To avoid that, he has been looking at hosting rewritten applications on a zLinux partition on the mainframe. "I can rewrite a piece of Cobol but closely interface with the mainframe program and database without jumping between a mainframe box and a distributed box," he says.

As for BNY Mellon's core systems, Brown says, "I see Cobol on the mainframe continuing on in perpetuity. Over half of our major applications are still on the mainframe. It offers the best scalability, reliability and availability for doing sequential processing."

Rebuilding the talent pipeline
The idea that Cobol and the mainframe are legacy technology is a perception issue, BCBS of SC's Ravindra argues. It's a mindset that has pushed students away from taking Cobol and other mainframe technology courses, and convinced schools that they shouldn't offer mainframe-related technologies in computer science curricula.

Despite efforts such as the 8-year-old IBM Academic Initiative, the talent pipeline hasn't kept up as the baby boomers who dominate today's mainframe shops begin to retire in larger numbers. "The market, universities and junior colleges aren't generating enough developers to replace those who are retiring," Gartner's Vecchio says -- a sentiment shared by Emard.


Previous Page  1  2  3  4  5  6  Next Page 

Sign up for CIO Asia eNewsletters.