A recent talk with ScreenJet's Alan Yeo shed some light on the migration process for 3000 owners. Our era is not the first time anybody has made a migration in the 3000 world. This one is different, however, from the transition the entire community performed about 25 years ago. That was an era when HP rolled out radically new hardware, but had engineered a way to carry program code forward. There was work, however, that everyone had to do.
In the fall of 1988, moving from MPE V to MPE XL was being called a migration. In the same way that today's migrations are being shaped as transitions or modernizations, the migration of MPE V systems to a new OS was attempting to avoid being labeled a conversion. Big work, that conversion stuff. Migration, by everybody's measure this year, is bigger stuff than replacing an app while moving off a 3000.
Yeo said this month that a customer of his had already made their migration once -- a "proper migration" if you can imagine the British accent -- and was returning to do another migration. "They're happy they migrated, because they now know that they can," he said. Yeo estimated that about one in every five companies that have left have done this proper migration -- which means keeping business logic and lot of MPE code in hand during the move.
Today's strategy for migrating has much in common with what 3000 owners were doing in 1988, the time when MPE XL was first coming online at customer sites. Victoria Shoemaker of Taurus Software wrote an article in the HP Chronicle that month called From MPE V to MPE XL: Migration Made Easy. Her seven steps make up that year's proper migration: Education; analysis; developing a migration plan; MPE/V conversion; installation of HP-PA RISC machines; Compatibility Mode operation; Migration to Native Mode operation.
Planning is the single most important element of your migration. Regardless of how many applications that run in your shop, how many machines you have, how much third-party software you run, your migration's success depends on how well you have planned it. Spend the time to plan. It pays off.
There are some differences between the advice you can check out in the PDF of that archive article from the HP Chronicle versus the counsel you'll get today. In late '88 there was not much of a thriving market of experts who were selling professional services for getting onto a new hardware platform with a new OS. HP set up Migration Centers in five US cities, plus one in Germany. You'd bring in code and run it on the new Series 900 HP 3000 system, then resolve errors and get time to do rewriting as needed. The centers even included shredders, so your sensitive data and coding wouldn't be compromised.
But nobody inside HP was doing that work. And travel with your tapes and printed code was essential to using that help. You'd apply for some time on some very new computers, and an even newer OS. The timesharing era wasn't that far in the past. It didn't seem a tremendous throwback.
Today there's other options. You can even have that migration planning done for you after a series of interviews at your own site. Or simply phone calls, after you've sent information over this thing we call the Internet. Didn't exist in 1988, to be sure. You could transfer your files via a terminal emulator, of course. The concept of remote system access and inventory was a rare thing indeed.
Tens of thousands of 3000 sites survived and even thrived after the MPE V to XL migration. HP created a Compatibility Mode to operate the old programs unmolested. Performance was actually worse in many cases in that early migration era, because MPE XL 1.x was a slow and unpredictable release. Operating in Native Mode at least made the brand-new Series 950 and 925 servers as fast as existing top-end Series 70s. Like today's ultimate generation of HP's 3000 iron, Hewlett-Packard was certainly leaving a widely-installed field of hardware behind.