If your code is complete, up-to-date, and does not have any outside dependencies, the transition from Alpha to Integrity is a straightforward process of "re-compile, re-link, and re-qualify". While this approach works well, there are many obstacles that can prevent the use of this technique.

This presentation will explain how to migrate to Integrity when the easy approach is not feasible. Many ISVs, OEMs, and end-users have environments including hundreds or thousands of inter-dependent programs, often composed of a complex of products and custom software, maintained by a combination of outside organizations and internal teams. We will examine how to organize the migration of a large-scale environment from Alpha to HP Integrity, without user disruption or business risk.

Several areas will be reviewed, including:

• When to quickly migrate to HP OpenVMS on Integrity by re-compiling, re-linking, and re-qualifying
• Why many organizations cannot use an "all-at-once" strategy
• How unique OpenVMS capabilities allow organizations to assimilate HP Integrity servers in a phased, structured, extremely low-risk approach
• How OpenVMS clustering and image translation capabilities offer end-user management and technical staffs a unique degree of flexibility in transitioning to new architectures and equipment

Preceding this presentation will be a presentation on how the principles that enable this strategy are applicable to IT systems in general, Architectural Techniques for Interoperability and Coexistence, sponsored by the Ottawa Chapter of the IEEE Computer Society. IEEE and Encompass members, and the interested public are invited to both presentations.