Many people consider COBOL, which stands for COmmon Business Oriented Language, a true dinosaur. Since it was the very first of the high-level programming languages, it has been around since the time of the first mainframes, and that is what it was intended to run on. However, since memory was at a premium, the language had to be efficient. COBOL was used for all sorts of programming, and almost everything, until FORTRAN came along.
It is around to this day on all sorts of older systems that work, and deliver satisfactory results year after year. There are a group of COBOL programmers that do maintenance coding, and are kept fairly busy, because so many are under the impression that there is no need to know COBOL.
A story in today’s ComputerWorld tells us that perhaps that might be changing, as some of the big iron gets retired, yet the programs are still needed, and it is easier to move them to COBOL for the x86 platform, known as recompiling, than to recode them in another language, such as C, or C++.
A lot of Cobol-based applications have a plot line similar to the first Star Trek movie.
In it, the crew of the Enterprise discovers a huge, intelligent cloud they called “Veeger.” It turns out (plot spoiler alert), though, that Veeger was an unmanned spacecraft called Voyager that had been launched from Earth some 300 years earlier and then readapted by alien forces.
That Star Trek movie was released in 1979. The Cobol-based ERP application suite used by Owens & Minor Inc., a medical supply company, began its life in the 1980s as a packaged application. Over time, the company adapted the ERP software to meet its specific needs, creating a highly customized system with 10 million lines of code.
Today, the ERP system runs the company’s core business systems, including order and inventory management, purchasing, pricing, accounts receivable and accounts payable. Nearly 130 years old, Owens & Minor reported about $8 billion in revenue last year.
Unlike Veeger, the ERP system over time got a lot bigger, but not necessarily a lot better. Each green screen application had a different user interface, which required that the company buy larger and larger monitors to display the multiple windows, according to Rick Mears, CIO of the Mechanicsville, Va.-based firm.
Owens & Minor is in the process of modernizing its ERP system but the software will remain Cobol-based.
Managers decided not to replace the system with a new one or to rewrite the code in a more modern programming environment like Microsoft’s .Net. The company instead took a third path — moving the Cobol-based ERP system, including its Unix-emulator, off a mainframe computer to an x86 server and Windows clients. Mears said the business logic built into the ERP system was too valuable to lose.
A lot of companies replace Cobol systems or rewrite them because they don’t like the interface, Mears said. He compared such a move to razing a house that only needs restoration. “There are all sorts of stories of companies taking on nine figure rewrite projects. I don’t understand the payback for that,” he said.
Mears said he is convinced that either replacing or rewriting the ERP system would have cost $100 million to $200 million more than what the firm is paying to move it from the mainframe to the x86 servers.
“Many companies who purchase an off-the-shelf ERP system proceed to spend tens or even hundreds of millions to modify the package to meet their business requirements,” he said.
The Owens & Minor approach to modernize the ERP system allowed it to reduce spending on hardware. Although the Owens & Minor isn’t disclosing exact figures, the cost of operating the new x86 system including migration cost was less than half of the cost of operating its 700 MIPS (millions instructions per second) mainframe.
The argument of whether to use mainframe and distributed environments is longstanding among IT shops, where there are strong opinions on each side.
Bank of America, for instance, is so committed to the mainframe that the company works with IBM to ensure that colleges and universities produce sufficient numbers of graduates with the skills needed to run and use them.
IBM mainframe revenue had been consistently rising until last year when it declined nearly 29%. But that result wasn’t unexpected in bad economic times. In fact, 2009 worldwide server revenue for systems by all makers declined by almost 19% to $43.2 billion, according to IDC. In addition, IBM is releasing a new System z computer this year, and its mainframe revenue typically declines prior to the release of a new one.
So not only will COBOL survive, it looks like the mainframe will be surviving for a while longer too.
The thing about COBOL is that it is very natural. Once you get started, and know a bit of syntax, you can really get rolling, in a way that does not happen with any “modern” language.
Even working with some of the now older, but meant to be very user friendly 4GLs like Smalltalk, was really no easier than programming in COBOL.
Maybe it should make a comeback on a limited basis.
from this -
It’s not called COMMON Business Oriented Language for nothing.
≡≡≡≡≡≡≡≡≡≡ Ḟᴵᴺᴵ ≡≡≡≡≡≡≡≡≡≡