|
HP OpenVMS Systemsask the wizard |
|
The Question is: What do I need to upgrade from V5.5-2 to the latest OpenVMS release. I need also the cost of the upgrade kit for VMS 5.5-2 , 6.2 for Y2K. Regards The Answer is :
You will need to read the manuals that describe the upgrade process
for each of the releases you upgrade through as well as for the target
OpenVMS release, as well as the associated new features and release
notes manuals for each intervening OpenVMS release and the target
OpenVMS release.
The available OpenVMS upgrade paths are listed in the OpenVMS Frequently
Asked Questions (FAQ) -- please see below for the V7.2 update to this
information; this update and more recent information will be included
in future editions of the OpenVMS FAQ.
The OpenVMS Wizard is able to answer technical questions, pricing
and availability questions should be directed to your local or
regional Compaq representative, or to your Compaq reseller.
Information on the Y2K CD-ROM kit is available from the Y2K pages
referenced by the OpenVMS FAQ.
The OpenVMS FAQ is available from the Ask The Wizard page, as well
as from:
http://www.openvms.digital.com/
--
MGMT16. What are the OpenVMS version upgrade paths?
Note: See "OpenVMS Alpha Terminology" section, below.
OpenVMS Alpha release upgrade (or update) paths:
From V1.0, one can upgrade to V1.5.
From V1.5, or V1.5-1H1, one can upgrade to V6.1.
From V6.1, one can upgrade to V6.2.
From V6.2, one can update to V6.2-1H1, V6.2-1H2, or V6.2-1H3.
From V6.1, or V6.2, one can upgrade to V7.0.
From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0, one can upgrade to V7.1
From V6.1, V6.2, V6.2-1H(1,2,3), V7.0, V7.1-1Hx, or V7.1-2, one
can upgrade to V7.2.
From V7.1, one can update to V7.1-1H(1,2)
From V7.1, one can upgrade to V7.1-2
From V7.1-2, one can upgrade to V7.2
Some typical OpenVMS Alpha upgrade (or update) paths are:
V1.0 -> V1.5 -> V6.1 -> (V6.2, V7.0, or V7.1, V7.2)
V6.2 -> V6.2-1H3
V1.5-1H1 -> V6.1 -> (V6.2, V7.0, or V7.1)
V6.2-1H(1,2,3) -> V7.1
V7.1 -> V7.1-1H(1,2)
V7.1 -> V7.1-2
V7.1-1H(1,2) -> (V7.1-2 or V7.2)
V7.1 -> V7.2
Note that OpenVMS Alpha V7.0 does not include support for hardware
and/or configurations first supported in OpenVMS Alpha V6.2-1H1,
V6.2-1H2, or V6.2-1H3; one must upgrade to OpenVMS VAX V7.1.
One cannot update directly to a V6.2-1Hx Limited Hardware Release
(LHR) from any release prior to the baseline V6.2 release. The
same prohibition holds for performing updates directly to V7.1-1Hx
from any release prior to V7.1 -- this is not supported, and does
not produce the expected results. The LHR kits can, however, be
directly booted and can be directly installed, without regard to
any operating system that might be present on the target disk.
OpenVMS Alpha updates for LHRs (through V7.1-1Hx) require the use
of VMSINSTAL for the update. These LHR releases use PCSI for the
installation, but not for the update. Non-LHR releases use PCSI
for installs and upgrades.
OpenVMS Alpha V7.1-2 and later use PCSI for the installation of
OpenVMS ECO kits. Earlier releases use VMSINSTAL-based ECO kits.
OpenVMS VAX release upgrade paths:
From V5.0 through V5.4-3 inclusive, one can upgrade to V5.5.
From V5.5, V5.5-1, or V5.5-2HW, one can upgrade to V5.5-2.
From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0.
From V5.5-2, V5.5-2H4, or V6.0, one can upgrade to V6.1.
From V6.0, or V6.1, one can upgrade to V6.2.
From V6.1, or V6.2, one can upgrade to V7.0.
From V6.1, V6.2, or V7.0, one can upgrade to V7.1.
From V6.1, V6.2, V7.0, or V7.1, one can upgrade to V7.2.
Some typical OpenVMS VAX upgrade paths are:
V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.0, V7.1, V7.2)
V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, V7.1, or V7.2)
V6.1 -> (V6.2, V7.0, or V7.1, V7.2)
Note that OpenVMS VAX V6.0 does not include support for hardware
and/or configurations first added in OpenVMS VAX V5.5-2H4, one
must upgrade to OpenVMS VAX V6.1.
OpenVMS VAX releases use VMSINSTAL for the installation of ECO
kits for all releases.
OpenVMS Cluster Rolling Upgrades:
Rolling Upgrades require multiple system disks. Rolling upgrades
permit the VMScluster to remain available while individual systems
are being upgraded to a new OpenVMS release.
OpenVMS Cluster rolling upgrades for both OpenVMS VAX and OpenVMS
Alpha may (will) have different, or additional upgrade requirements,
and have requirements around which versions of OpenVMS can coexist
in an OpenVMS Cluster than what is listed here.
See the _OpenVMS <platform> Version <Version> Upgrade and Installation
Manual_, and the OpenVMS Software Product Descriptions
(http://www.openvms.digital.com/openvms/spd/list.html) for further
details on the rolling upgrade, and for support information. The
documentation for older releases of OpenVMS VAX includes various
platform-specific manuals, manuals that include instructions that
are specific to installing and upgrading on the platform.
Layered Product and Support Information:
For information on Prior Version support, see:
http://ww1.digital.com/services/mcs/mcs_priorversion.htm
For information on supported versions of layered products, and
minimum required layered product versions, see:
http://www.openvms.digital.com/openvms/os/swroll/index.html
For information on the release history of OpenVMS, including
information on the code names of various releases and the
major features:
http://www.openvms.digital.com/openvms/os/openvms-release-history.html
Additional release history information, as well as a variety of
other trivia, is available in the VAX 20th anniversary book:
http://www.openvms.digital.com/openvms/20th/vmsbook.pdf
OpenVMS Alpha Terminology:
update: Typically used for Limited Hardware Releases (LHR)
releases. Performed via VMSINSTAL. Applies only
to the OpenVMS release that the LHR is based on,
or to an intermediate LHR. (eg: V7.1-1H2 applies only
to V7.1-1H1 and to V7.1, not to any other releases.)
LHRs within a series are cumulative, containing all
files and features of previous LHRs in the same series.
upgrade: Performed via PCSI. Upgrades can typically be applied
to a release-specific (and documented) range of prior
OpenVMS releases.
install: Performed via PCSI. With an installation, no existing
version of the operating system is assumed present, nor
are any files from any copy of the operating system might
be present preserved, and the entire contents of the target
disk are destroyed via a disk initialization.
preserve: Performed via PCSI. Otherwise similar to an installation,
this option skips the disk reinitialization. User files
on the target disk are preserved. Any existing operating
system files on the target disk are clobbered.
LHR: Limited Hardware Release. LHRs are specific to and are
targeted at new hardware configurations, and are not
shipped to customers with support contracts. At least
one LHR kit must be specifically acquired when purchasing
new hardware, new hardware that is not (yet) supported by
any mainline (non-LHR) release. LHRs have an "H" in the
OpenVMS version string, indicating a "Hardware" release.
|