They don't pay enough. That's the issue. If COBOL paid as much or better for the average developer than Java, there would be no shortage of COBOL developers.

The contract offers my mother received involved good money, but that was actually part of the problem. She got the impression that most of the managers at "Big Corp" had little/no regard for these "critical" systems; they were just looking to save their own jobs, either by way of a miracle worker (wave a magic wand and fix 40 years of tech debt in 3 months) or a fall guy (it's the contractor's fault, not mine).

Also, COBOL work is kinda crap. Debugging 20-year-old Java code sucks, but a 40-year-old COBOL project, with source code backed up to 5-inch floppy disks - forget about it. (I just watched the trailer for 'The Many Saints of Newark'. LOL)

It needs to be breathtaking money to be worth it when you take into account the risk of investing in a shrinking skill set

I think it depends. On my side, I'm OK with a modest salary if it's stable for the next 10-20 years. I think mainframe fits perfectly. It's declining but not that fast. It's unattractive so you face little competition. It's just a hell lot hard to get in in the middle of your life.

You can get that with a regular developer job with the threat of your job being a dead end.

Good point. Maybe new developer salary is different from what contractors get? The number I see for contractors are pretty good but yeah they have decades of experience under their belt.

I would imagine part of the reason is because even if you have a trained COBOL maintainer, they still have to learn and understand the actual business logic of the application. Learning the language is not even half the battle. Maintaining old often undocumented code is a hard task in any language.

Indeed, I've once met someone who migrated a COBOL project to Java, the biggest complain wasn't even the Language itself, but extracting business logic from a 40-year old spaghetti codebase. Sometimes bugs where part of the business logic itself and other developers who consumed the monstrosity had to make corrections on their side.

> I wonder why those big companies don't hire someone new and train them

They don't have enough work to train them on and whatever they have is actually critical enough to need someone experienced.

My partner was hired to be a COBOL programmer right out of college in 2004 & trained to work on AS/400s.

The problem was that everything was a small part of a big project, but you got no experience building a big project over its lifetime to see how it should be done. And on top of it, a lot of things which were "the right way" in 1991 wasn't so great in 2005. So a lot of work was actually bringing the existing work to code before you could do the tiny bit of work which is actually needed.

Pay me a lot of money and I’ll do it. I think they all want to pay like 5 figures though.

It seems to be all the same story. People talk about these huge pays and guaranteed jobs but the average developer is already getting a huge pay and has no problems finding work.

The pays for COBOL do not even look that compelling and you are walking down a dead end when these systems finally modernize. I wouldn't touch cobol for anything short of $300k and the promise of enough work that I could retire within a few years.

When my friend immigrated to Canada he quickly realized that one of the fastest ways to make decent money (he is not an entrepreneur) is in IT. Being very intelligent guy he decided that there should not be too much of a problem for him to learn programming. To my surprise out of various areas he had chosen to do COBOL stuff. Long story short - he has very secure employment, not the top but very nice salary and zero worries.

Smart guy :P

They are. The largest bank here in Sweden for example offers a 6 month free COBOL Academy to newly graduated students, that ends in basically a guaranteed job.

I guess there just aren't enough takers.

That's very good. I never saw these in Montreal. Maybe because I'm not a new graduate.

I originally got into mainframe tech through IBM's annual Master the Mainframe program [1] which got me limited access real mainframe on some college's campus and IBMs manuals.

The old -- and likely not so bad -- advice if you'd like to learn how to use a Mainframe is: Get access to a one, get a copy of latest Red Book [2], and start playing around :)

[1]: https://www.ibm.com/it-infrastructure/z/education/zxplore (this isn't the program I went through, but my old bookmark now redirects here)

[2]: https://www.redbooks.ibm.com/abstracts/sg248852.html (IBMs mainframe Technical Guides traditionally have a red cover)