I don't get it..The old system is written in cobol, it stores data in a complex way built apoun years, and fo this reason to do simple thing its a pain in the ass ok. So one have to design a new system, with a "modern" technology approach, that doesn't need to be similar to the old, it has just to be good, safe easy to maintain. Then populate the new database from the Cobol's one (i have to know which kind and type of data i need in my new current system). run and test the new system as soon as everything works fine, then shutdown the old one. In the end it s not just extract all the data and inject it in the new system? Am i missing something?
this post was submitted on 29 Mar 2025
562 points (100.0% liked)
Bluesky
1115 readers
7 users here now
People skeeting stuff.
Bluesky Social is a microblogging social platform being developed in conjunction with the decentralized AT Protocol. Previously invite-only, the flagship Beta app went public in February 2024. All are welcome!
founded 5 months ago
MODERATORS
I took a college COBOL class in 1979. I had to write my program out on stacks of punch cards. Had to stand in line at the computer center for the grad students to run it on the University computer. They just gave you a "it ran" or "it failed" and a printout on sheets of those endless rolls of papers with perforations and holes on both sides?
Good times.