11 ms·
The problem really isn't COBOL. COBOL is not a difficult language. It reads almost like English sentences. Any competent programmer would not be challenged by C
by ams6110 10y ago
The problem really isn't COBOL. COBOL is not a difficult language. It reads almost like English sentences. Any competent programmer would not be challenged by COBOL. The problem is all the glue. JCL, SNA, CICS, ISM, ISPF, etc.
It's like the difference between Java (the language) and J2EE, except in the context of 1970s computer technology. It's not intuitive and not something you can really work through without a lot of training and experience.
- jwilliams 10y agoIndeed - and although COBOL is the topic here, the issues are pretty similar with J2EE. There are a lot of legacy J2EE applications in banking and finance. Let alone the skills and inside knowledge you need to know the various containers and modern(ish) glue (WebSphere is the prime example). Underlying this is that banks used to see IT/Technology as competitive advantage. A lot of tech came directly out of the banks. IT became a cost-center in the 90s and it was never the same. The irony is that this tech stack was pretty good and fit-for-purpose for a lot of banking workloads. Plus it kept working... so that just lessened the investment required.
- clumsysmurf 10y agoAt my last employer, there were a few "mainframers" (we called them). I was curious so I would ask my mainframer coworker how things worked on his end. I always struggled to understand, because it seemed everything was different ... the terminology, the culture, the ideas. I couldn't use analogy to tie what he was describing back to what I knew.
- tyingq 10y agoMakes sense, as there's little in common for many base concepts. You deal mostly in stream files, they probably deal mostly in record oriented files..where their "kernel" understands it's record oriented. Your terminal emulator sends every keystroke the the host. Theirs doesn't send anything until they specifically make it do so. You have ASCII or utf8, they have EBCDIC. Some of it is crossing over though. They used to talk about virtual machines before they were common for us. The concept was confusing at the time.
- nsxwolf 10y agoYou got that right. I had to deal with an interesting banking file format and I asked a question on Stack Overflow and got this gem of an answer. I politely accepted it as the right answer but boy oh boy does it feel like it's from an alien civilization. http://stackoverflow.com/questions/28640159/what-is-the-difference-between-a-variable-blocked-format-and-a-fixed-blocked-for http://stackoverflow.com/questions/28640159/what-is-the-diff...
- sundvor 10y agoWow. That answer took some time and a whole lot of knowledge to write up, so definitely deserved the "accepted" - but if that's just the surface of things I understand why it's like a different world.
- deleted 10y ago[deleted]
- Fuzzwah 10y agoI just lost a chunk of time checking out the user who supplied the answer: http://stackoverflow.com/users/1927206/bill-woodger http://stackoverflow.com/users/1927206/bill-woodger This one was great: http://stackoverflow.com/questions/15008999/can-anybody-tell-me-what-language-is-this http://stackoverflow.com/questions/15008999/can-anybody-tell...
- redm 10y agoThe IBM EXEC 2 manual (second edition 1982) is an interesting scan/read too. http://bitsavers.trailing-edge.com/pdf/ibm/370/VM_SP/Release_2_Jun82/SC24-5219-1_VM_SP_EXEC_2_Rel_2_Reference_Apr82.pdf http://bitsavers.trailing-edge.com/pdf/ibm/370/VM_SP/Release...
- BillWoodger 10y agoThanks for looking, I hope you didn't feel it lost in a bad way :-)
- Fuzzwah 10y ago
- rdiddly 10y agoYeah even though COBOL is called out by name here, the problem these guys are getting paid to solve seems like as much of a "domain knowledge" or "business rules" problem as a language one.
- acdha 10y agoAlso just half a century of accumulated practice. Before Y2K I used to hear so many stories of people changing or removing things and then finding out that e.g. some manager in a different division depended on a report which needed these two “unused” variables.