Ads by TechWords

See your link here
Receive the latest technology news and information.
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
Cloud Computing
View all newsletters




Privacy Policy
 

Rebuilding the legacy -- modernizing mainframe code

Millions of lines of mainframe code need to be modernized. How to do that -- and what to keep on the mainframe -- is the trillion-dollar question.

April 24, 2006 12:00 PM ET

Computerworld -

By some estimates, the total value of the applications residing on mainframes today exceeds $1 trillion. Most of that code was written over the past 40 years in Cobol, with some assembler, PL/1 and 4GL thrown into the mix. Unfortunately, those programs don't play well with today's distributed systems, and the amount of legacy code at companies such as Sabre Holdings Corp. in Southlake, Texas, makes a rewrite a huge undertaking. "We're bound by our software and its lack of portability," Sabre Vice President Alan Walker says of the 40,000 programs still running on IBM Transaction Processing Facility (TPF), Agilent Modular Power System and other mainframe systems.

Alan Walker, vice president of Sabre Holdings
Alan Walker, vice president of Sabre Holdings
With a shortage of Cobol programming talent looming in the next decade and a clear need for greater software agility and lower operating costs, IT organizations have begun to make transition plans for mainframe applications. The trick lies in figuring out which applications to modernize, how to do it and where they should reside.

Applications fall into one of three groups based on scale, says Dale Vecchio, an analyst at Gartner Inc. Applications under 500 MIPS are migrating to distributed systems. "These guys, they want off," Vecchio says. As organizations begin peeling away smaller applications, they may move to a packaged application; port the application to Unix, Linux or Windows; or, in some cases, rewrite the applications to run in a .Net or Java environment, he says.

Dale Vecchio, an analyst at Gartner Inc.
Dale Vecchio, an analyst at Gartner Inc.
In the 1,000-MIPS-and-up arena, the mainframe is still the preferred platform. Applications between 500 and 1,000 MIPS fall into a gray area where the best alternative is less clear. An increasingly common strategy for these applications is to leave the Cobol in place while using a service-oriented architecture (SOA) to expose key interfaces that insulate developers from the code.

"If you expose those applications as a Web service, it's irrelevant what that application was written in," says Ian Archbell, vice president of product management at tool vendor Micro Focus International PLC in Rockville, Md. "SOA is just a set of interfaces, an abstraction."

"SOA at least allows you to break the dependency bonds," says Ron Schmelzer, an analyst at ZapThink LLC in Waltham, Mass.

Cobol isn't going away, but it's also not moving forward. While the Cobol code base on mainframes is projected to increase by 3% to 5% a year, that's mostly a byproduct of maintenance, says Gary Barnett, an analyst at Ovum Ltd. in London.



Jump to comments

TPF system

Additional Resources

WHITE PAPER
Approximately 60 percent of data migration projects overrun time or budget, while some fail completely. Download this white paper, "Enhancing Your Chance for Successful Data Migration," to learn the critical steps you need to take to execute a data migration project with minimum cost and risk to your business.
WHITE PAPER
Read the Gartner research note to learn why the TCO of a server-based computing deployment used to deliver all applications to users is around 50% lower than that of an unmanaged desktop deployment.
WHITE PAPER
Economic downturns have a tendency to accelerate emerging technologies, boost the adoption of effective solutions, and punish solutions that are not cost competitive or that are out of synch with industry trends. This IDC White Paper presents the results of an IDC survey of 330 companies in Western Europe, Asia/Pacific and the Americas that measures the receptiveness to Linux and takes into consideration changing views driven by the disruptive economic environment that businesses face today.