ClearPath OS 2200 Series Release 13.2 Software Planning and ...

Migration Planning Checklist
7.1. Migration Planning Checklist
Use the following checklist to help plan your migration strategy. Depending on the
configuration of your site, you may have additional issues to consider.
• If you are migrating an existing Dorado 400, Dorado 4000, or Dorado 4100 system to
this release from a prior release, there are critical interdependencies involving
CPCommOS, various plateau components, and the installation order for certain
products (including the EXEC). Refer to sections “7.9 Migration for Dorado 4000”
“7.10 Migration for Dorado 400” or “7.11 Migration for Existing Dorado 4100
Customers” for details.
• Perform an audit of all Unisys software levels that you currently have installed.
• Perform an audit of the local code that you have installed, and plan for its migration.
If you have a significant amount of local code and plan to carry it forward to this
release, you should estimate the complexity of this task. This estimate should
include the number of programming hours required to relocate the code, the amount
of testing needed, and the environment required for recertification.
• Perform an audit of all PLEs applied to the current levels of standard software.
Verify that these PLEs are already integrated into levels for this release. If not,
generate the levels for this release with PLEs.
• Plan your installation sequence. Know which products you will be installing and in
what order. See Appendix C for the tape name of each product.
• You will receive a product key tape that provides access to the authorized products
for your site. You must register that key tape using the SOLAR level received with
this release before installation.
• After registering the key tape, print and save the SOLAR PKGREG Key Package
Summary Report. This report identifies the products that you are authorized for.
• Plan a training strategy for programmers, operators, and end users.
• Arrange system time for installation and testing.
• Arrange for additional technical assistance. Estimate the amount and type of work
and dedicate appropriate personnel to specific tasks.
• Plan for a fallback position in case you have to crossboot back to your previous
environment.
• Back up your current software and data files.
• Do not make site program changes until you have the new release up and running.
• Before upgrading to use new capabilities, be sure your existing production system is
stable.
• Make sure that you have the corresponding product documentation available and
study it ahead of time for preparation.
• If a document refers to a problem list entry (PLE), obtain a listing of that PLE from
the Unisys Product Support Center.
• Update your in-house documentation (of site-specific procedures).
7–2 7831 0349–043