> LOTS of legacy COBOL still has our financial and insurance markets working smoothly.
Is there any proof for such a statement? Has anyone seen business applications written in COBOL running on any thing then maybe a few mainframes in a few US agencies/corporations that haven't been replaced simply because they aren't broken (yet!)?
I know there's tons of Fortran and some PL/I code that will never be translated in any other language anytime soon because it's just good the way it is, but COBOL? I'm starting to think that this whole "COBOL will still be around in 100 years" is an urban myth...
If you would spend 2 minutes to do a google search for businesses still using COBOL you'll find your answer. My statement is based on professional experience in the IBM Midrange field talking with people who still work on these systems. Use this link as a jumping off point http://www.guardian.co.uk/technology/2009/apr/09/cobol-inter... (not much has changed in this space in the last 4 years, this space moves extremely slow when it comes to change at the systems level)
If you use a charge/credit card, are an electric customer, had prescription filled, an insurance claim adjudicated, etc.…, your transaction was processed through some COBOL code.
Yes, corporate system overlords would like to put these systems to rest, but that a task easier said than done, with a great deal of business intelligence buried in the code.
Is there any proof for such a statement? Has anyone seen business applications written in COBOL running on any thing then maybe a few mainframes in a few US agencies/corporations that haven't been replaced simply because they aren't broken (yet!)?
I know there's tons of Fortran and some PL/I code that will never be translated in any other language anytime soon because it's just good the way it is, but COBOL? I'm starting to think that this whole "COBOL will still be around in 100 years" is an urban myth...