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 ETComputerworld -
![]() | |
| Alan Walker, vice president of Sabre Holdings |
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.
"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.
TPF system
Additional Resources



White Papers & Webcasts
Oracle Accelerate - Not Just Smart but Timely
Download Now!
Why BI is Ripe - Now! - For Businesses of Any Size
Download Now!
Showcase ISV Products with BIRT
View this now!
Create Mashups in ISV Applications
View this now!
HP Technology Guide for Scalable Business Solutions
Download This Resource Now!
Maximize the Value of ISV Applications
View this now!


