The resurgence of COBOL is of no surprise. Expanded as Common Business Oriented Language, COBOL might not even feature in the university curriculum, and that’s why there are fewer COBOL developers. But the matter is that this programming language is used by legacy systems on which the world still depends, for their day-to-day transactions. Almost 70 to 80 percent of worldwide present-day business transactions are done on IBM iSeries. A 2017 research study uncovered billions of lines of COBOL codes, which are still in use today.
But there is a gap that needs to be bridged. Legacy AS/400 systems that run COBOL applications need COBOL developers. for regular maintenance and new application development. Existing legacy server infrastructures that run on AS/400 are irreplaceable. Government institutions, large banks, public services companies, insurance companies, etc. – all of them are unwilling to stop AS/400 systems and upgrade to the newer IBM Power Systems.
Their argument is simple – when something is running super-fine, why change just for the sake of change?
Why cannot COBOL be Replaced?
AS/400 COBOL applications are used all over the world, and there is always a need for COBOL developers. Considering that more than 100,000 AS/400 customers exist, one can imagine the enormity of COBOL application deployments and the increasing need for COBOL developers.
- More than 60 million patients are treated and cared for with applications developed on AS/400 COBOL apps. Thanks to the efforts of the COBOL programmer.
- Most ATM transactions, at least 90% of them are powered by COBOL application.
- Every year, almost 96% of vacations are booked using systems built on COBOL developers of all ages.
- Social Security Administration has more than 60 million lines of code written in COBOL.
- IRS uses COBOL applications; about 50 million lines of COBOL code are used at this single entity.
Has Something Better Come Along?
The answer is – that it is not required. For so many business applications, COBOL has been a rock-solid foundation. COBOL applications haven’t broken, are resilient, and secure. So, the need to replace it does not arise because if a system is working fine, then there is no need to tinker with it. Another point of consideration is that COBOL has explicitly been designed for business applications. Other low-level programming languages such as Fortran and LISP are better suited to solve scientific problems and create artificial intelligence applications.
Grace Hopper’s Graceful Language Has Come a Long Way
At the beginning of the computer age, banks, government organizations, and insurance companies started creating machine-specific programming languages with the help of COBOL developers. Due to the high cost and time involved in running and maintaining these applications, a universal solution was needed in place. And Grace Hopper was instrumental in bridging, this gap by creating COBOL. The programming language was universal and capable to run on all business systems.
COBOL’s syntax is an output of Grace’s reasoning that the syntax of programming languages should be close to spoken languages. That’s why COBOL syntax was considered a wordy one by COBOL developers. The era of verbose English-like programming languages has dawned again, starting with Python. Grace’s reasoning of yore is now very relevant because the humanization of computing increases the possibilities of unlimited programmatic expressions.
Read More: https://www.integrativesystems.com/cobol-developers/