HP3000/HP 3000 FAQ

Last Updated: Thursday, February 01, 2007 02:38 PM

How do I upgrade from a classic HP3000 to PA-RISC

2.1.3. How do I upgrade from classic to PA-RISC

I am going to update my classic HP system to an MPE/iX system. What special considerations should I bear in mind and/or expect?

JK

For the most part, you can simply use the provided utilities to migrate your accounting structure, restore your files, and run compatibility mode just fine. There are, of course, certain exceptions to this rule. The following list is *not* comprehensive (caveat emptor) but include:

* Anything using Privileged Mode (in-house, 3rd party, or HP-supplied).

* Anything calling COMMAND to invoke non-MPE/iX supported commands such as PTAPE, any caching-related commands, private volumes, and other specifics.

* Any code looking for PARM= or INFO= by tracing stack markers (depends on release of MPE and MPE/iX).

* Anything dependent on system log files.

* Anything dependent on LDEVs being < 255 or device type/subtype info.

When you start converting your code to "native mode" there are other considerations, such as alignment issues (persistant problem with any converted applications), switch stubs (if you have RL/SL linkages), and floating-point data conversion issues (the "Classics" used an HP format, while "Spectrums" use the IEEE format).

However, don't dismay, things are much better now (time-proven) than they used to be, but it is rarely if ever a "recompile and go" scenario.

2.1.3.1. Are there any hidden costs upgrading MPE/V to MPE/iX platform?

JK

Yes - most all HP and third-party software must have a license upgrade to run on the new system, plus maintenance charges. You might consider upgrading to a (large) production CPU with no utilities and a small system for program development, compilers, debuggers, etc to save . Some third-parties do not charge (Robelle, 3k Associates, Adager, (?)).