![[Compaq]](../../images/compaq.gif)
![[Go to the documentation home page]](../../images/buttons/bn_site_home.gif)
![[How to order documentation]](../../images/buttons/bn_order_docs.gif)
![[Help on this site]](../../images/buttons/bn_site_help.gif)
![[How to contact us]](../../images/buttons/bn_comments.gif)
![[OpenVMS documentation]](../../images/ovmsdoc_sec_head.gif)
| Document revision date: 19 July 1999 | |
|
|
|
|
|
|
| Previous | Contents | Index |
This chapter contains information that applies to installations and upgrades of the OpenVMS VAX and OpenVMS Alpha operating systems. It also provides information specific to certain hardware.
The installation and upgrade notes in this chapter are organized into the following categories:
Hardware and firmware notes follow the upgrade and installation sections.
For information about layered product installation and support, see
Chapter 2.
1.1 Compaq's Support Policy
In November 1996, DIGITAL announced a revised support policy and a new Prior Version Support Service for customers concerned that software release cycles and the end of support may not be aligned with their ability to migrate systems to the new software releases.
Compaq is continuing these support policies. In keeping with the November 1996 policy, support is available for the current version and the previous version (for up to 12 months) when a customer purchases a standard support contract.
For versions of software older than the previous version, Prior Version Support service is available in two levels of support, including full, remedial support on selected products and versions. This year, extended Year 2000 support was announced to provide regular remedial support through 30--JUN--2000 for OpenVMS VAX and Alpha Version 7.1 and OpenVMS Alpha Version 7.1--2.
For more information about all levels of support, contact your Compaq
support representative or visit the Compaq
Services web site.
1.2 Installation and Upgrade Information Common to VAX and Alpha
The following release notes document installation and upgrade
information common to both platforms. For additional Alpha specific
notes, see Section 1.4.
1.2.1 Changes and Enhancements
This section describes information related to installing or upgrading
the OpenVMS VAX and OpenVMS Alpha Version 7.2 operating systems.
1.2.1.1 Networking Options
V7.2
OpenVMS provides customers with the flexibility to choose the network protocol of their choice. Whether you require DECnet, TCP/IP, or OSI, OpenVMS allows you to choose the protocol or combination of protocols that works best for your network. OpenVMS supports both Compaq and third-party networking products.
During the main installation procedure for OpenVMS Version 7.2, you have the option of installing the following Compaq networking software:
Or, after you install OpenVMS, you can install a supported third-party networking product of your choice.
For information about how to configure and manage your Compaq networking software after installation, see the manuals listed in Table 1-1. The manuals in online format are available on the OpenVMS Documentation CD-ROM and can be ordered in printed format through DECdirect (800-344-4825).
| DIGITAL TCP/IP Services for OpenVMS | |
|---|---|
| DIGITAL TCP/IP Services for OpenVMS Installation and Configuration | AA--LU49L--TE |
| DIGITAL TCP/IP Services for OpenVMS Management | AA--LU50K--TE |
| DECnet-Plus for OpenVMS (Phase V) | |
| DECnet-Plus for OpenVMS Installation and Basic Configuration | AA--QPSUB--TE |
| DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration | AA--QPSVB--TE |
| DECnet-Plus for OpenVMS Network Management | AA--R1UHA--TE |
| DECnet for OpenVMS (Phase IV) | |
| DECnet for OpenVMS Guide to Networking | AA--PV5ZA--TK |
| DECnet for OpenVMS Networking Manual | AA--PV60A--TK |
| DECnet for OpenVMS Network Management Utilities | AA--PV61A--TK |
V7.2
TCP/IP is the preferred network transport for OpenVMS Version 7.2. Customers can also install DECnet, with DECnet-Plus being the recommended DECnet product.
If you choose to install the TCP/IP transport, DIGITAL TCP/IP Services for OpenVMS, Version 5.0, will be installed using the POLYCENTER Software Installation utility on both OpenVMS VAX and Alpha systems. The configuration from earlier versions of TCP/IP Services will be preserved and used as a basis for the TCP/IP Services for OpenVMS Version 5.0 configuration. If you do not choose this installation option and have TCP/IP Version 4.1 or 4.2 installed on your system, the earlier version will be left on your system and will still be available for use.
TCP/IP Services for OpenVMS, Version 4.2 and earlier are not supported on OpenVMS Version 7.2. Compaq strongly recommends that you run only supported versions of TCP/IP Services for OpenVMS. Unpredictable behavior can result if you run unsupported software.
Although DECnet-Plus remains the recommended DECnet, both DECnet-Plus
and DECnet Phase IV can be installed from the OpenVMS Version 7.2
installation procedure. To get support for any version of DECnet Phase
IV, you need a Prior Version Support contract.
1.2.1.3 Upgrading Systems Running PATHWORKS V6.0/6.0A for OpenVMS (Advanced Server)
V7.2
The following products ship with OpenVMS Version 7.2, providing file and print services:
Versions of PATHWORKS for OpenVMS prior to PATHWORKS V6.0B for OpenVMS (Advanced Server) are not supported on OpenVMS Version 7.2.
To migrate systems currently running PATHWORKS V6.0/6.0A for OpenVMS (Advanced Server), follow these steps:
Refer to Section 2.2 for more information about the Advanced Server
for OpenVMS. Refer to Section 2.15 for information about restrictions
pertaining to PATHWORKS for OpenVMS products on OpenVMS Version 7.2.
1.2.1.4 DECevent Version 2.9 or Later Required to Analyze Errors
V7.2
Starting with OpenVMS Version 7.1--2, DECevent Version 2.9 or later is required to analyze error log files.
In OpenVMS Version 7.0 and earlier releases of OpenVMS, the DECevent DCL command DIAGNOSE was defined during the operating system installation or upgrade.
When you install OpenVMS Version 7.2, the DIAGNOSE command is disabled. To enable the DIAGNOSE command, you must install DECevent Version 2.9 (in the DECevent kit provided on the OpenVMS Version 7.2 CD-ROM) after you install OpenVMS Version 7.2.
If the DECevent kit provided on the OpenVMS CD-ROM is not installed after the operating system, users attempting to use the DIAGNOSE command will receive the following system message:
$ DIAGNOSE [parameters] %DIA-E-NOINSTAL, DIAGNOSE has not been installed on this system |
For more information about DECevent, see Section 4.6.1.1.
1.2.1.5 OpenVMS Cluster Compatibility Kits for Version 6.2 Systems
V7.1--1H1
The OpenVMS Cluster Compatibility Kits that shipped with OpenVMS Version 7.1 have been superseded by remedial kits ALPCLUSIOnn_062 for Alpha systems and VAXCLUSIOnn_062 for VAX systems. These kits are required for OpenVMS Version 6.2 systems that are members of an OpenVMS Cluster system that includes systems running one or more of the following OpenVMS versions:
The kits contain the OpenVMS Version 7.1 enhancements to Volume Shadowing, Mount, lock manager, and other quality improvements for OpenVMS Version 6.2 systems as well as additional enhancements to these subsystems made after the release of OpenVMS Version 7.1. The kits also contain limited support for SCSI device naming using port allocation classes.
These remedial kits are included on the OpenVMS Version 7.2 CD-ROM. You can also obtain these kits from your Compaq support representative or from the following web site:
This section documents an upgrade and installation condition that is
common to both VAX and Alpha operating systems.
1.2.2.1 PCSI-I-RETAIN Messages During DECnet-Plus Installation
V7.2
If you upgrade to OpenVMS Version 7.2 and your old system has either DCE for OpenVMS or DECnet-Plus for OpenVMS installed on it, when you install DECnet-Plus, you will get PCSI-I-RETAIN informational messages for the following files:
For example:
%PCSI-I-RETAIN, file [SYSLIB]DTSS$RUNDOWN.EXE was not replaced because file from kit does not have higher generation number |
You can ignore these messages. The DECnet-Plus kit has been properly
installed.
1.3 Installation and Upgrade Information Specific to VAX
The release notes in this section pertain only to installations or
upgrades of OpenVMS VAX operating systems. See Section 1.2 for
additional notes that pertain to both VAX and Alpha systems. For
complete information about installing or upgrading to OpenVMS VAX
Version 7.2, refer to the OpenVMS VAX Version 7.2 Upgrade and Installation Manual.
1.3.1 Changes and Enhancements
The following note describes a change in magnetic tape distribution of
the OpenVMS VAX operating system.
1.3.1.1 Magnetic Tape Distribution
V7.2
The OpenVMS VAX Version 7.2 kit is available on two, 6250 BPI, open reel magnetic tapes. (Earlier versions of OpenVMS VAX shipped on four 1600 BPI magnetic tapes.)
The first tape contains the VMS072.A, VMS072.B, and VMS072.C save sets. The second tape contains the VMS072.D, VMS072.E, and VMS072.F save sets, and the DECW072.C, DECW072.D, DECW072.E, and DECW072.F save sets. For more information about locating files on the distribution media, consult the OpenVMS VAX Version 7.2 Upgrade and Installation Manual.
Distribution of the OpenVMS VAX operating system on magnetic tape is now available only to customers who subscribe to the OpenVMS VAX Media and Hardcopy Documentation Update Service.
OpenVMS VAX CD-ROM and TK50 kits are available from all of the following sources:
The following notes describe problems that can occur when installing
OpenVMS VAX Version 7.2.
1.3.2.1 Error at Shutdown After Booting CD-ROM for Full Environment Installation
V7.2
When you select to shut down the system (option 2) after booting a CD-ROM during a full OpenVMS VAX environment installation, you may encounter a problem on certain CPU types. However, these problems do not adversely affect the installation. The problems affect the following CPU types:
V7.2
When performing a full OpenVMS VAX environment installation from CD-ROM, do not attempt to change the displayed system time, even if it is incorrect. Attempting to change this value results in a write lock error that requires rebooting the CD-ROM to recover.
This problem does not occur during a standalone BACKUP environment installation.
You can change the system time once the installation has completed.
1.4 Installation and Upgrade Information Specific to Alpha
The release notes in this section pertain only to installations or
upgrades of OpenVMS Alpha operating systems. See Section 1.2 for
additional notes that pertain to both Alpha and VAX systems. For
complete information about installing or upgrading to OpenVMS Alpha
Version 7.2, refer to the OpenVMS Alpha Version 7.2 Upgrade and Installation Manual.
1.4.1 Changes and Enhancements
This section describes a change in the memory requirements for OpenVMS
Alpha systems.
1.4.1.1 64 MB of Memory Required
V7.2
Starting with OpenVMS Alpha Version 7.2, a minimum of 64 MB of memory
is required.
1.4.2 Problems and Restrictions
This section describes problems and restrictions that apply to
installing or upgrading to OpenVMS Alpha Version 7.2.
1.4.2.1 BAP System Parameter Tuning Required
V7.2
The CIPCA, CIXCD, KFMSB, and Qlogic 1020ISP adapters are the first among an expanding list of adapters to use bus-addressable pool (BAP). BAP is a non-paged dynamic, physical-address-filtered memory pool used to overcome I/O bus and 32-bit adapter physical addressing limits.
Starting with OpenVMS Alpha Version 7.1, BAP allocation is controlled by system parameters. If one or more system adapters use BAP, you must adjust the following BAP system parameters after installing or upgrading the operating system:
You can do this automatically using AUTOGEN with the FEEDBACK qualifier. The typical AUTOGEN with FEEDBACK command to set these parameters follows:
$ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT FEEDBACK |
If you prefer not to use this command because you want to adjust only the BAP parameters settings, you can use the following procedure:
| AGEN$FEEDBACK Data | System Parameter | Units |
|---|---|---|
| BAP_MIN | NPAG_BAP_MIN | bytes |
| BAP_MAX | NPAG_BAP_MAX | bytes |
| BAP_MIN_PA | NPAG_BAP_MIN_PA | Mb. PA 1 |
| BAP_MAX_PA | NPAG_BAP_MAX_PA | Mb. PA 1 |
The BAP allocation amount depends on the adapter type, the number of adapters, and the version of the operating system. The size of physical memory and the I/O bus determine whether the BAP remains separate or is merged with normal nonpaged dynamic memory (NPAGEDYN).
The general rule that determines whether BAP remains separate follows:
For systems whose BAP is merged with nonpaged pool, the initial amount and maximum amount of nonpaged pool (as displayed by the DCL command SHOW MEMORY/POOL/FULL) do not match the value of the NPAGEDYN and NPAGEVIR system parameters. Instead, the value of the NPAG_BAP_MIN system parameter is added to NPAGEDYN to determine the initial size, and the value of NPAG_BAP_MAX is added to NPAGEVIR to determine the maximum size.
On OpenVMS systems with merged BAP, the values of the NPAGEDYN... system parameters typically need to be increased. After your system has been running a few days, you can adjust these values by one of the following three methods:
V7.2
For OpenVMS Alpha Version 7.2, the DECwindows Motif V1.2-5 kit is provided in reference format. Usually the DECwindows kit is provided in sequential format; reference format is being used to work around a performance problem.
In sequential format, the DECwindows kit appears in a single file on the OpenVMS operating system CD-ROM. In reference format, the kit is expanded. The individual files that make up the kit are in the [DWMOTIF_ALPHA125.KIT...] directory hierarchy.
Do not mistake the Product Definition File (PDF) for the kit. The PDF (file DEC-AXPVMS-DWMOTIF-V0102-5-1.PCSI$DESCRIPTION) is only part of the kit.
The differences between reference and sequential format make no difference in the installation or upgrade procedure. Regardless of how PRODUCT command operations are executed, they work identically with either format.
Copying the Reference Format Kit
Do not attempt to copy the reference format kit by using a DCL COPY command. Instead, use the PRODUCT COPY command with the /FORMAT=SEQUENTIAL qualifier, so that the kit is copied to a single-file, sequential format kit.
For example, if the OpenVMS Alpha operating system CD-ROM is located on DKA400 and you want to copy the DECwindows Motif V1.2-5 kit to the [KITS] directory on DKB100, you might use a command similar to the following:
$ PRODUCT COPY DWMOTIF /VERSION=V1.2-5 /FORMAT=SEQUENTIAL - _$ /SOURCE=DKA400:[DWMOTIF_ALPHA125.KIT] - _$ /DESTINATION=DKB100:[KITS] |
This command creates file
DKB100:[KITS]DEC-AXPVMS-DWMOTIF-V0102-5-1.PCSI, which is a sequential
format DECwindows Motif kit. This file can be copied using the DCL COPY
command.
1.4.2.3 Remove Java Version A1.1 Before Upgrading
V7.2
If you have Java Version A1.1 installed, you must remove it before upgrading to OpenVMS Alpha Version 7.2. You can reinstall Java Version A1.1 after performing the upgrade, but you must remove it again before the next upgrade.
If you have a later version of Java installed, you do not need to remove it before upgrading OpenVMS. For your convenience, Java Version 1.1 is included on the OpenVMS Version 7.2 media. |
To remove Java from a running system before upgrading, use the following command:
$ PRODUCT REMOVE JAVA
|
You can also remove Java when you perform the Version 7.2 upgrade.
Select Option 6, "Remove installed products." When prompted, enter the
device for your target system; then select Java from the list of
products.
1.4.2.4 Spiralog File System Not Supported
V7.2
Spiralog has been retired and does not work with OpenVMS Version 7.2.
If Spiralog is installed on your system, you must deinstall it before upgrading to OpenVMS Version 7.2. |
V7.2
When upgrading a version of DIGITAL TCP/IP Services for OpenVMS Alpha that is earlier than Version 5.0, you may encounter the following error:
%PCSI-I-PRCOUTPUT, output from subprocess follows ... %LIBRAR-E-LOOKUPERR, error looking up UCX in $4$DKA300:[SYS0.SYSCOMMON.][SYSHLP]SDA.HLB;1 -LBR-E-KEYNOTFND, key not found %PCSI-E-EXERMVFAIL, product supplied EXECUTE REMOVE procedure failed %PCSI-E-OPFAILED, operation failed Terminating is strongly recommended. Do you want to terminate? [YES] |
This error can occur when you are upgrading DIGITAL TCP/IP Services as part of an OpenVMS upgrade, or during a separate TCP/IP Services upgrade. When the old version of TCP/IP Services is removed, it attempts to remove the module UCX from the SDA Help library. However, if OpenVMS has been upgraded since TCP/IP Services was installed, the SDA Help library has been replaced by a new library and the UCX module that TCP/IP Services inserted into the old SDA Help library is not found.
This problem can also occur if you attempt to remove DIGITAL TCP/IP Services for OpenVMS.
The workaround to upgrade or remove DIGITAL TCP/IP Services is to answer "NO" to the question "Do you want to terminate?" A NO response allows the operation to complete.
Normally you should answer "YES" (the default) to the "Do you want to terminate?" question unless Compaq (or another software provider) specifically instructs you to answer otherwise under certain circumstances, such as this. |
V7.2
The following error can occur when removing DIGITAL TCP/IP Services for OpenVMS (UCX) Version 4.2:
%PCSI-I-PRCOUTPUT, output from subprocess follows ... %DCL-E-OPENIN, error opening PCSI$SOURCE:[000000]CLEAN_SDA_HELP.COM; as input -RMS-F-DEV, error in device name or inappropriate device type for operation Portion done: 10% %PCSI-E-EXERMVFAIL, product supplied EXECUTE REMOVE procedure failed -RMS-F-DEV, error in device name or inappropriate device type for operation %PCSI-E-OPFAILED, operation failed Terminating is strongly recommended. Do you want to terminate? [YES] |
The workaround to upgrade or remove DIGITAL TCP/IP Services is to answer "NO" to the question "Do you want to terminate?" A NO response allows the operation to complete.
Normally you should answer "YES" (the default) to the "Do you want to terminate?" question unless Compaq (or another software provider) specifically instructs you to answer otherwise under certain circumstances, such as this. |
V7.2
If you are performing a rolling upgrade from Version 6.2 or Version
6.2--x to Version 7.2, and are using MEMORY CHANNEL adapters
(CCMAA-xx), see Section 4.14.2.10.1 for special instructions before
you upgrade.
1.4.2.8 X.25 Version 1.0--G and Earlier Not Supported
V7.2
X.25 Version 1.0--G and earlier will not operate on OpenVMS Version
7.2. If you upgrade to OpenVMS Version 7.2 from OpenVMS Version 6.2,
you must remove X.25 Version 1.0--G before you upgrade. Compaq
recommends that you install X.25 Version 1.2 and X25ALP_MUPA012 (the
mandatory update kit for X.25 Version 1.2A) during the operating system
upgrade.
1.4.2.9 X.25 Version 1.1--B for OpenVMS Alpha Crashes OpenVMS Version 7.2
V7.2
Customers using X.25 Version 1.1--B for OpenVMS Alpha should install X.25 Version 1.2 and X25ALP_MUPA012 (the mandatory update kit for X.25 Version 1.2A) before installing OpenVMS Alpha Version 7.2. Failure to do so will result in a system crash when X.25 starts up.
If you install X.25 Version 1.2 over Version 1.1--B or Version 1.1--B ECO01, you will get a number of warning messages.
If the X.25 Version 1.1--B ECO03 product, called X25ECO03, has been installed on your system, Compaq strongly recommends using the command PRODUCT REMOVE X25ECO03 to remove X25ECO03 before you install X.25 Version 1.2. If you do not remove X25ECO03 before installing the X.25 Version 1.2 kit, you must respond to PRODUCT error and warning messages to prevent the installation from terminating. Removing X25ECO03 after installing Version 1.2, can result in the uwanted removal of some files associated with Version 1.2.
| Previous | Next | Contents | Index |
|
|
| privacy and legal statement | ||
| 6534PRO_001.HTML | ||