Migrations probably begin with an application review that shows too much at stake to stay with MPE. It's not the OS of the 3000 that's found wanting, however. Usually there's a decline in support for a subsystem, or a development environment (think 4GLs). The 3000's databases have the same support ecosystem they've had for awhile: Third parties (indies) with database tools and expertise, or one company selling an IMAGE-compatible database for non-3000s. It's good to have the 3000's data structures known and emulated.
But migrations, once they're triggered by M&A or boardroom jitters or exiting 3000 staff, need a database. Here in the first week of March we're marking the one-year anniversary of the Oracle Stink Bomb. That's what the company threw at HP's enterprise customers who use Unix. Oracle won't develop for the HP-UX version of that database any longer. Your database choices in a migration have drifted away from the obvious.
While Oracle thinks that's a great way to turn HP's Unix customers into Sun Unix customers, the last year hasn't delivered the riches of database FUD to Oracle. Former HP CEO Mark Hurd has been explaining away a lack of Sun uptick at recent analyst meetings. Instead of Sun, HP's Unix users who wanted to migrate to a more stable DB environment are choosing IBM. Big Blue, after all, is still selling its iconic DB2 for Itanium servers.
It's worth noting that Speedware's legacy modernization services, and migration team, has been working with IBM customers for quite awhile. AS/400 accounts have been in that company's pipeline. DB2 has got to be familiar to one of the two remaining Platinum Migration Partners. A couple of research houses have whitepapers that report on IBM's success in taking away Oracle accounts. It's an odd mix but might be a potent one, if your migration budget is deep enough: HP's Unix, plus IBM's database.
We'd be remiss to omit what we consider the obvious migration database choice for 3000 sites: Eloquence. This is the only database ready to work with IMAGE conventions.
But if Eloquence isn't a big enough household name to sell a migration, well, "nobody ever got fired for buying IBM," the saying goes. (It's not all roses inside the Big Blue corral. We just heard from a 3000 shop whose IBM email system started rejecting all inbound mail for a day.) DB2 might qualify as the Next Most Obvious Choice for a migration database replacement. While Oracle continues to tick off more than 140,000 HP Unix customers, all to toss some coal in the Sun boilers, it's been making opportunity for IBM. At the least, for the IBM software group. IBM's got price advantages it can apply to make choosing DB2 look attractive. How can it do that? There's the IBM Services operation to counteract any database discounting. What IBM gives away in DB2 it gets back in system-wide support for HP servers.
While you might not be thinking of hiring IBM to support an HP-UX system, you're definitely not thinking about hiring Sun and Oracle to support that system. Not after the full year of Oracle Stink Bombing. Birket Foster of MB Foster pointed us to a useful website about the impact of the bombing, Conor O'Mahony's Database Diary. You'll find IBM DB2 Welcomes Oracle Database/HP Itanium Customers up there, a shelter from the stink bombs.