Those high salaries won't generally motivate an "in it for the tech", startup-friendly developer of the type that commonly frequents HN... but a bank with a legacy mainframe system probably doesn't want to hire that person, and they don't need to. The technology isn't the core of their business.
On the other hand, there are many highly competent developers out there who view their job as a means to an end, a way to support their family/life/hobbies/etc. To these people, learning a highly specialized legacy skill and making lots of money is exactly the right motivator.
As an example, I present my father. He has been writing data management software for hospitals for decades, and does all his work on midrange IBM AS/400 ("System i") systems. He writes all his code in IBM RPG--"report program generator" code. In recent years he's learned Java, C and Unix systems to keep himself fresh, but he's never found the need to actually use any of those skills, or a job using these that would treat him as well as his legacy work.
I wonder how long it will take before Java becomes the next COBOL (unless it already has...)
I won't call Java the "next" COBOL until COBOL goes away. Which I predict will happen sometime between 2050 and the death of the sun...
You would need to pay me a lot of money to convince me to work with COBOL full-time. Once you've convinced me to do the job, paying me more won't make me any better at it.
For .NET the "wall" is 30-50k $. For COBOL the "wall" seems to be 50k$ + (I'm conservative about this estimate on purpose). So beyond this "fair" compensation for ones troubles, the pay doesn't scale anymore.
So It's not that people wouldn't want to work with COBOL or perceive It as sexy - It's just that the "sexiness" point is a couple of 10's of thousands of dollars higher then for other tech.
The rules a company follows at small sizes and large sizes are not necessarily entirely the same, especially once bureaucracy sets in.
Both of these things can't be true!