A lively discussion is in play at the HP 3000 Community of LinkedIn, where users, developers and managers are examining issues around migrating away from an MPE application of serious size and age. Or the need to do so.
Once Randy Thon mentioned he's using MM/3000 to manage maintenance services at Cessna Aircraft -- adding that the company's looking at options to leave the 3000 -- others in the 425-member community supplied advice and counsel.
The options suggested to Thon go beyond using the new Stromasys emulator. He's pleased with the way his app is working on the 3000 for Cessna. The hardware is the burr under the aircraft maker's saddle. The migration of an app like MM/3000 is a project that taxed every aspect of the software's owner, a crew laden with ex-HP engineers.
"The eXegeSys team spent years trying to migrate MM/3000 to Unix and ultimately gave up," said Jeffrey Lyon, "and sold the intellectual property. 11.7 million lines of COBOL, SPL, and Pascal is a big beast to move."
There's also the issue of whether you would get what you were really pursuing, once you'd complete a migration. These are different issues for a software vendor than a user of its products. Have a look at the chat and chime in with your own experience about migration strategy.