3 ms·
Hi! First post on here. The conversion/adapter tools exists. It's not a technical issue. The problem is that cobol applications are normally monolithic, and a
by bitfhacker 8y ago
Hi! First post on here.
The conversion/adapter tools exists. It's not a technical issue.
The problem is that cobol applications are normally monolithic, and a migration to another system represents an huge risk because:
1) you migrate like a Big Bang migration, or;
2) you migrate step by step.
Imagine a bank with applications running at 30 or 40 years without problems... Nobody in his perfect judgment will accept to have a Big Bang migration. The risk is too high.
For migrating step by step, you must have a good bussiness case (it must compensate the risk), opportunity (you must be able to keep working in the Bussiness As Usual) and you must have the right people (people that have the knowledge in organization). If you don't have this three things it will be very hard to migrate Cobol to another language/platform.
Usually Cobol is used in mainframe, so the right aproach (with less risk) IMHO is to migrate first COBOL from z/os to a Cobol in another platform (windows/*nux whatever), and then migrate Cobol gradually to another language.
- rectang 8y agoThere can also be an intermediate phase of migrating from a hardware mainframe to a virtualized mainframe. I understand that's what TicketMaster did a while ago. > Hi! First post on here. Welcome, and very nice post. :)