This section provides important information that
can affect the success of your upgrade. Review the cautions, restrictions,
and notes carefully before you begin the upgrade.
4.3.1 Upgrade Paths
following subsections describe the various types of upgrades to OpenVMS
126.96.36.199 Direct Upgrade Paths
You can upgrade directly to OpenVMS Integrity
servers Version 8.4 from only the following versions of OpenVMS Integrity
You can upgrade directly to
OpenVMS Alpha Version 8.4 from only the following versions of OpenVMS
188.8.131.52 Indirect Upgrade Paths
you are running a version of OpenVMS Alpha earlier than Version 7.3-2,
you cannot upgrade directly to Version 8.4. You need to perform intermediate
version upgrades before upgrading to Version 8.4. HP recommends performing
the various upgrades over a several-day period, allowing for system
disk backups between upgrades. This allows to look for, and recover
from, problems that might arise because of a specific upgrade. This
also allows you to identify the exact point in the upgrade stream
where the problem arises.
For example, if you are running OpenVMS
Alpha Version 7.1, you need to perform an intermediate upgrade to
either Version 7.2, 7.2-1, or 7.2-2, and then upgrade to Version 7.3-2.
After this, you can upgrade to Version 8.4.
NOTE: When performing an intermediate upgrade, review each OpenVMS
installation manual available for the version of OpenVMS that you
are upgrading to, checking for any special requirements such as patches
that might have to be applied before upgrading.
4.3.2 Update License Requirements
IMPORTANT: Before upgrading to OpenVMS Integrity servers Version 8.4, you
must have the appropriate OE license loaded on your system. Similarly, before upgrading your OpenVMS Alpha
system, you must have the appropriate Alpha licenses loaded on your
HP software licenses grant the right to use the
current version of a product or any previous version of the product
at the time of purchase.
NOTE: When you initially purchase the OpenVMS software
and license, HP provides a Product Authorization Key (PAK) that is
required to enable the License Management Facility (LMF) to register
the license and to validate and authorize subsequent use of the product.
A PAK does not provide license or new version rights. For more information
about licensing and the License Management Facility, see the HP OpenVMS License Management Utility Manual.
If you need an Update License, please contact
your HP Sales representative.
4.3.3 Components You Choose Not to Install
If you choose not to install optional OpenVMS
networking software (DECnet or TCP/IP) or the DECwindows/Motif GUI
during the upgrade, the upgrade procedure removes these products from
the system disk. Note that TCP/IP Services for OpenVMS is installed
automatically when OpenVMS is installed by HP SIM provisioning. For information about checking for appropriate versions
of software on your system and for certain products requiring that
you manually remove older versions, see Section 4.4.
NOTE: Unless you have specific reasons to do otherwise, HP recommends
that you accept the defaults and install all OpenVMS options. OpenVMS
and layered products have various dependencies on many of these options.
Even if you think you do not need certain options, some OpenVMS or
layered product operations might not work correctly if other OpenVMS
options are not installed.
Note also that, for OpenVMS Integrity server installations,
the availability of certain options depends on the OE you have purchased.
For more information, see the HP Operating Environments
for OpenVMS for Integrity Servers Software Product Description (SPD 82.34.xx).
4.3.4 Licenses and Layered Products
The upgrade procedure is designed so that you
do not need to reinstall most layered products after the upgrade.
However, you might need to reinstall certain layered products because
of product-specific installation procedures.
The upgrade procedure leaves your OpenVMS license
and layered product licenses intact. You do not need to reinstall
these licenses after you upgrade.