As another webinar demo unspooled today for HP 3000 data migration products, the strategy of hold on or move onward demoed another facet. A 3000 might be a candidate for de-commissioning simply because the system has been too successful in the past. The next server will be different, but there's no guarantee the replacement will be better in significant aspects. Waiting for something better is not as easy as moving to something different.
Take COBOL compilers, for example. At the investment firm Fayez Sarofim, the HP 3000 was being evaluated for replacement. One element of the eval was finding a COBOL compiler compatible with the code running on the 3000. The company had to choose a way forward that was mostly different. Better was another phase.
"We chose AcuCOBOL over Micro Focus at the time of our migration because AcuCOBOL better handled the packed HP Floating Point without losing significant decimals," said George Willis. "It also had a more powerful set of debugging tools that were easy to use." Protecting decimal data was the priority. Getting a superior debugger was the improvement.
Time moved onward for the Sarofim strategy though, shifting away from apps and toward software services (SaaS). HP's Unix systems—an HP-UX 4466 Rx using AMXW, Cognos, Micro Focus COBOL, Suprtool and Warehouse—eventually got the boot, just like a 3000 did. The shift to services erased a department at the company. There's no emulation that can oppose that kind of sea change in strategy: "We don't even need our own servers, we'll access an app instead."
While making its move to HP's Unix, Willis said "We did not want to go through another riskier migration until we were stabilized. We are certainly stable now, but the firm has decided to move a different direction." So onward it went to SaaS. Emulation never got a fighting chance.
That's searching for something different, that talk of needing to be off the system before MPE/iX stops date-keeping in 2028. Ten-plus years is a long time, enough to enable the magic of making CALENDAR work in 2028 a reality, perhaps. It's not impossible, although someone has to do the work to salvage MPE's date capability for 2028 use.
The silver lining for the 3000 community in any migration story is that the business often goes to a vendor who's been in the market a long time. MB Foster is one player like that, demonstrating its roots with a demo like today's of UDACentral. MB Foster celebrated its 40th anniversary in the 3000 market this week. 'The HP3000 market is our home market," Birket Foster said in an email today, "and we are grateful for the support, suggestions and collaboration with us."
Stanfield is looking for customer stories about migrating with Fresche Legacy, which earned its 3000 reputation as Speedware.
He had specific questions and would appreciate an email in reply.
1. What system did you convert to (Unix/Windows/Linux)?
2. What system did you convert from(HP3000 A-class/N-class?) and how busy was the system? Number of users?
3. Are you still running that system?
4. Did you convert to using the Eloquence DB?
5. Performance after conversion: good or bad?
6. Any Do's or Don't's?
7. Primary Code base (Speedware/Powerhouse/Cobol/Fortran)? Amount of code converted?