Slashdot Mirror
3 Open Source Projects For Modern COBOL Development (opensource.com)
An anonymous reader writes: While Grace Hopper's contributions to computing are remembered, celebrated, and built upon by her successors, COBOL itself is often dismissed as a relic of earlier era of computing. To a certain extent, that is true. Most of the COBOL being written today is for maintaining legacy code, not starting new projects. However, the language is still being updated, with COBOL 2014 being the most recent standard for the language, and there are still plenty of opportunities to apply for jobs that require COBOL experience. In an article on Opensource.com, Joshua Allen Holm highlights three open source projects that are keeping the language alive.
"A modern computer without Cobol and Fortran is like a chocolate cake without the ketchup and mustard"
(Source unknown).
http://abstrusegoose.com/323
Yes, Visual COBOL is a real thing: http://www.microfocus.com/downloads/visual-cobol-23-datasheet-215624.aspx
According to MF, '...supports Cloud, mobile, .NET and JVM, and a wide range of the latest environments.", so go out there and build your next Web 11.0 (we're up to that by now, right?) app in COBOL*
* MF is not responsible for any resulting substance abuse or psychiatric issues you may experience
I've often wondered if jobs for more obscure languages (such as Cobol) pay more. Any idea what a Cobol programming job typically pays compared to a C/C++ job?
How about instead we pound a wooden stake through its heart, burn the body, salt the ashes, apply holy water, weld it into an iron urn covered with runes and annointed with the boold of seven virgins and bury it at a crossroads under a full moon?
GnuCOBOL: it translates COBOL into C and GCCs it into software. I'll skip the whole COBOL stage personally.
OpenCOBOLIDE: it's like notepad but with COBOL highlighting rules.
NodeCOBOL: it uses GnuCOBOL to splice the generated C-code into Node.js based programs.
These won't keep COBOL alive or anything like that, but they might serve as a way for experienced COBOL programmers to keep using their skills for things other than maintaining old awkwardly written mainframe software.
Modern app appers app apps in APP languages, like AppScript and AppApp! Only LUDDITES who still use LUDDITE hardware like keyboards still use COBOL!
Apps!
>> three open source projects that are keeping the language alive
Open Source ain't keeping COBOL alive. It's IBM. If all those legacy apps could be ported off the mainframe and run at scale, they'd potentially lose billions of dollars.
If all COBOL code suddenly stopped working, well, how are your stone knives and bearskin making skills? Banks, insurance companies would fail, and then goes the rest of the interconnected economy.
Does anyone still doing COBOL have hair on their head?
Not like the horseshoe ring of hair just on the sides, but like hair on the top?
And no, a bushy beard and a baseball cap doesn't disguise the fact you are bald.
Today cobol is a glue language for ibm tech like CICS, IMS, VSAM, DB2, etc - it has all the bindings, crud, copy books, tools, and junk to link that legacy universe together - so open source cobol is useless since it doesn't have all that stuff - no one cares about cobol, they just use it as a glue language for the ibm crud because it's well established and there are already a bazillion lines of it - no one is going to rewrite CICS transactions in python - but new development in the ibm world is mainly done with websphere and java - the old cobol code is for business logic encoded in transactions - modern stuff puts things on a message queue which is then processed by some kind of batch transactions - so cobol will always be around.
There's an oxymoron if I ever heard one.
People still use Visual Basic and Java in their most recent incarnations, so why shouldn't we have modern versions of other terrible languages?
Dewey, what part of this looks like authorities should be involved?
No open source project is keeping Cobol alive. The Cobol world is barely aware of open source. Cobol is being kept alive by the billions of lines of code that do things like get you your paycheck or process your insurance claim every day.
People still use Visual Basic and Java in their most recent incarnations, so why shouldn't we have modern versions of other terrible languages?
No reason to insult Cobol in such a manner and put it on one level with Visual Basic and Java.
We suffer more in our imagination than in reality. - Seneca
Banks, insurance companies would fail, and then goes the rest of the interconnected economy.
I don't think so. Banks and insurance companies mostly run on Java. They began switching away from COBOL decades ago. Few applications are still in COBOL, and even fewer of those are mission critical.
I work in a decidedly legacy field -- airline IT. I'm not a mainframe programmer, but I do work a lot with these systems and see what it takes to care for and manage business-critical processes. I certainly wouldn't recommend learning COBOL as a primary skill these days, but having some diverse systems experience is useful. I have been very lucky and have been able to steer my IT career into very "cross-platform" companies that has given me tons of knowledge that I otherwise wouldn't have. It can't hurt to at least have some familiarity with different technology; I've gotten interviews and jobs simply because I have at least seen a few systems that employers have used and needed someone with a passing knowledge of.
Hanging out with mainframe guys, I hear the contracting job market is actually semi-decent. It's shrinking and not stable by any means, but people who really know both systems programming and a business domain can make tons of money on contracts. The problem is that, for better or worse, companies are stuck with the mainframe for quite some time to come. Ancillary stuff is being migrated off to save on processing -- IBM leases you the hardware and charges you monthly by the MIPS to use it. However, for a lot of companies, decades of business logic is buried in the core transaction processing code. Their choices are to try to pull all this COBOL logic out into something Java-y or just keep it running. Often, keeping it running is seen as cheaper and less risky. In particular, the airline stuff I work with has layers and layers of upstream stuff relying on the base system never changing. The systems integration work that will be needed to eventually pull this stuff out into a different environment is going to be enormous when it does happen, and it will be a fun project for the right kind of insane people.
That said, CIOs and the like are always trying to get rid of or offshore mainframe work. It's seen as legacy crusty stuff, not sexy like phone apps and the like. That contract market I talked about often has work for seasoned mainframe guys to come back and fix the disaster that HP or Tata or Infosys made when they took over mainframe operations, often the same people the company fired. There are also the "onshore hand-holders" that help the offshore guys when things get crazy. Regardless, there will always be pressure to get off the mainframe, and the workforce is retiring right now. The move will happen one day, but it will be extremely painful for some companies and industries. So, having a tiny bit of experience, even if it's "I've seen this before" kind of experience, can be useful in the long run. Not all of IT is exciting or cutting edge -- there are plenty of systems that are just -there- and just have to run.
I had the typical ignorant disdain of COBOL until I actually worked with some. Over a short period of time, I developed respect for the language and for the disciplined, methodical programmers who wielded it. We could learn much from reading old COBOL programs, particularly for web forms, where a modern form of COBOL would be a lot more readable and maintainable than the krufty PHP and JS that infests the web.
One small example is the COBOL institution of edit masks, which were invaluable for handling form input and output of things like phone numbers and credit card numbers. COBOL's edit masks were simple to use, readable and understandable, and powerful enough to cover common business cases. No modern web language has anything that approaches COBOL's elegance in this area, which is why entering your credit card on a web site is slow and tedious.
"GnuCOBOL GnuCOBOL (formerly known as OpenCOBOL) is a modern, open source, COBOL compiler. It works by translating COBOL code into C and compiling the code using GCC. "
Modern COBOL is like Military Intelligence - it does not exist.
Those who fail to learn from history are doomed to repeat it.
No single saying exemplifies IT or programming as much as this. When I was young I thought I was a hotshot and there was a gray hair telling me I'm not doing anything new. Now I'm a gray hair thinking the same thing and I've seem many things implemented and reimplemented in newer languages. It's a bit disheartening the lack of creativity. Essentially, if you don't think you can't learn anything from COBOL, you should probably get into management.
I've learned to respect older (retired???) COBOL programmers. Many worked with fewer resources than I have on my servers and with fewer tools. It's amazing that despite having more tools, more defined methodologies and modern languages, the functionality of many programs hasn't increased by much. A lot is merely window dressing, prettier screens.
COBOL for .NET is not designed for use with big iron.
Keep COBOL weird!
Banks, insurance companies would fail, and then goes the rest of the interconnected economy.
I don't think so. Banks and insurance companies mostly run on Java. They began switching away from COBOL decades ago. Few applications are still in COBOL, and even fewer of those are mission critical.
You're so wrong. Google "amount of COBOL used today" you'll see the real story.
"IBM estimates that more than 200 billion lines of COBOL code are still being used across industries such as banking..."
Banks, insurance companies would fail, and then goes the rest of the interconnected economy.
I don't think so. Banks and insurance companies mostly run on Java. They began switching away from COBOL decades ago. Few applications are still in COBOL, and even fewer of those are mission critical.
That would be no more than two decades there my friend, since the Y2K issue started being dealt with and Java even existed. Hate to tell you, but there is still quite a bit of COBOL code in the financial sector still doing "mission critical" tasks. Money people use the philosophy of, if it ain't broke don't fix it so we can keep profits and bonuses high. Do a quick search for COBOL programmer job and you'll find hundreds of openings, most in the financial sector.
I don't know how far I'd go in making that assumption either way. Lots of odd things come up when you deal with legacy systems. For example, we were working to replace a "mission critical" server over the course of six months or so (among other jobs too). However, sometime in the course of that, turns out someone bumped the power button and no one noticed for at least an additional month after we did.
On another one there was an old PC running on a desk that hadn't been used in years. No one had physically touched it for quite some time and the last guy who used it moved to another job years ago. One of the IT guys notices while doing something else, asked about it, filed the ticket and powered it off. The next day, a bunch of calls go into the desk about problems with various systems. Turns out that random PC had a server on it for something, which prevented some programs from running when it was off and ultimately cost a department a day's worth of work.
COBOL is not awkwardly written. You've just warped yourself into the hivemind so horribly that you think that software must be abstracted into objects. COBOL is written in the same logic as are business processes. COBOL is an elegant and surviving solution to a challenge of translating from the language of business to the language of computers. While these modern concepts like guis and noql and object oriented programming have their purpose, they are merely distractions for business computers. There's no need for them, and GUIs are merely an input method, not a value to the class of problems that COBOL solves well.
"A modern computer without Cobol and Fortran is like a chocolate cake without the ketchup and mustard"
As Scott Colvey, a writer for The Guardian wrote in 2009, ''Cobol is to business what the combustion engine is to motoring: it has been around so long, and installed in so many places, that doing something different would be impossibly costly.''
Eighty percent of the world's daily business transactions rely on a 59-year-old programming language called Cobol, short for "Common Business Oriented Language." Global commerce depends so much on Cobol that if its' 220 billion lines of installed code were mysteriously erased business would be catapulted back to the "B-Commerce" era.
As in "barter."
If you run hardware long enough, it breaks. If you run software long enough, it works. Cobol works. As the CIO of a Fortune 350 firm who requested anonymity because he didn't want to be associated with a story about Cobol, told me, "Cobol is the most extraordinarily efficient programming language ever written."
Cobol Is Dead. Long Live Cobol!
[Oct 2. 2014]
I was working in banking wire transfer those "decades ago". Plain and simple, you are wrong. Mainframe code was thoroughly COBOL on mostly MVS systems with not a thought of migrating to other machines or languages. Wire transfer was COBOL with other code being machine dependent. Many larger banks not using mainframes for it used Tandem machinery - COBOL, Tal, Tacl, with little or no Java except some terminal interface (even then, minor).
Even more wrong.
All that PeopleSoft customization results in generated COBOL, which is then compiled with MicroFocus COBOL.
Our main policy administration system is written in COBOL along with several others. Little to no Java.
Wooden armaments to battle your imaginary foes!
And nothing of value was lost
100 billion are pointless but needed statements telling the program the next thing is stop, then runs stop
I tried to guess before reading. At least one of these projects should be f COBOL compiler. Yes.
There are more FORTH implementations in the world, than useful programs, written in FORTH.
There has been a significant and unending effort to get Microsoft to continue development of Visual Basic 6 (VB6) or Open Source it. Thus far neither have happened though Microsoft did break down and provide full support for VB6 in Windows 10. This ensures VB6 will be supported until 2025.