I've had a bunch of recent projects reverse-engineering old COBOL code, in financial services.
Mostly to figure out the best way to replace the old systems with something newer, so not really as a "COBOL dev", though.
Mostly to figure out the best way to replace the old systems with something newer, so not really as a "COBOL dev", though.
I heard a story about replacing COBOL with JavaScript ... and my skin still crawls thinking about it.
It sounds kinda crazy but with good change control, documentation, good relationship with the ETL team - it was pretty maintainable.
Yet another went to a different mainframe system that they already had. They had multiple systems (both mainframe and Unix) which did similar jobs due to acquisitions over the years, and they moved the still-active customers from the most expensive mainframe to one of the cheaper mainframes.