HP OpenVMS Systems Documentation
HP OpenVMS Alpha Version 7.3--2 Release Notes
1.8 SHADOW_MAX_UNIT Default Setting and Memory Usage
OpenVMS Alpha Version 7.3 introduced minicopy support in HP Volume Shadowing for OpenVMS. As part of the minicopy functionality, a new volume shadowing system parameter, SHADOW_MAX_UNIT, was introduced. On OpenVMS Alpha systems, the default value for this system parameter is 500, which consumes 24 KB of main memory. On OpenVMS VAX systems, the default value is 100, which consumes 5 KB of main memory.
If you do not plan to use Volume Shadowing for OpenVMS, you can change the setting to its minimum of 10 (which consumes 480 bytes of main memory). By setting the default to its minimum, you free up 23.5 KB of main memory on an OpenVMS Alpha system and 4.5 KB of main memory on a VAX system.
Recommendations for SHADOW_MAX_UNIT settings for volume shadowing are
discussed in the HP Volume Shadowing for OpenVMS manual.
The remainder of this chapter concerns associated products that might
affect the installation or upgrade of the OpenVMS operating system. See
Chapter 2 for more associated products release notes.
Starting with OpenVMS Version 7.3-2, some of the POLYCENTER Software Installation utility kits on the operating system and layered product CD-ROMs are provided in compressed format. You can identify these kits by their file types:
The compressed format was developed to save space on the CD-ROMs. A bonus is that user systems with a slow CD-ROM reader may experience a slightly faster installation time for compressed kits because less data must be transferred from the input device.
The installation of a compressed kit is completely transparent to the user; no qualifiers or special actions are required. The POLYCENTER Software Installation utility expands (decompresses) records on-the-fly as it installs the product, so no extra working disk space is required.
The POLYCENTER Software Installation utility supplied with OpenVMS Version 7.3-2 (and any later versions) can use compressed and uncompressed kits interchangeably. However, on versions of OpenVMS prior to 7.3-2, the compressed (.PCSI$COMPRESSED) kits cannot be read unless an appropriate POLYCENTER Software Installation utility remedial kit is installed. This remedial kit is expected to be available before the final release of OpenVMS Version 7.3-2.
As an alternative to installing a POLYCENTER Software Installation utility remedial kit on an earlier system, you can easily convert a compressed kit into an uncompressed format. You can use the PRODUCT COPY command on OpenVMS Version 7.3-2 to create a standard .PCSI kit from a .PCSI$COMPRESSED kit and then transfer it to the target system for installation. Use a command similar to the following to perform the conversion:
Not all kits provided on the OpenVMS Version 7.3-2 operating system and
layered products CD-ROMs can be installed on prior versions of OpenVMS.
Before you attempt to install a product on a prior version, consult the
product's documentation to determine whether this kit installation is
If you have installed any of the following kits:
and then you upgrade to Version 7.3-1 or higher, the following ACMS files might get deleted:
This will cause ACMS to fail after the upgrade. To avoid this problem (or recover from it), remove the old ACMS kit (select Option 6 "Remove installed products" on the installation CD main menu) and then install the ACMS_U1_044 kit either before or after you upgrade the operating system. This kit replaces the kits in the preceding list.
You can get the latest ACMS kit from the following web site (follow the version links to the ACMS_U1_044 kit):
1.9.3 COM for OpenVMS Upgrade in Clusters Running OpenVMS Version 7.2-1 or 7.2-1H1
If you are running COM for OpenVMS in a cluster running OpenVMS Alpha
Version 7.2-1 or Version 7.2-1H1, and you intend to do a rolling
upgrade, see Section 1.9.10 for information about how to upgrade your
DECevent Version 3.1 or higher is required to analyze hardware error log files on certain supported, earlier hardware platforms (for example, the 1200, 8400, GS60, and GS140 platforms).
When you install or upgrade to OpenVMS Version 7.3 or higher, the DECevent DCL command DIAGNOSE is disabled. If you are installing OpenVMS on a hardware platform that needs DECevent and its DIAGNOSE command, perform the following steps:
Otherwise, when you attempt to use the DIAGNOSE command, you will receive the following system message:
The System Event Analyzer (SEA) is now the supported error log analysis tool for OpenVMS and for later hardware platforms (for example, the DSnn, ESnn, GS80, GS160, and GS320 platforms).
Additionally, you can use the new Error Log Viewer (ELV) utility to quickly examine an error log file that was created on these later hardware platforms. ELV is integrated into OpenVMS Version 7.3-2, and can be accessed by entering the DCL command ANALYZE/ERROR_LOG/ELV.
For more information about ELV, refer to the ELV chapter in HP OpenVMS System Management Utilities Reference Manual.
If you have both a DECevent-supported platform and SEA-supported storage devices, you will need both DECevent and the System Event Analyzer (SEA). Likewise, if you have both an SEA-supported platform and DECevent-supported storage or other devices, you will need both tools.
To install SEA, you must install the latest version of WEBES (Version 4.2 or higher). The current version of the DECevent kit is Version 3.4.
For detailed information about operating system requirements and supported hardware for DECevent, refer to the DECevent Release Notes, which are at the following web site:
Follow the "Download the documentation" link.
For detailed information about operating system requirements and supported hardware for SEA, refer to the WEBES Installation Guide, which is with the other WEBES documentation at the following web site:
For more information about DECevent, refer to the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.
When you install or upgrade to OpenVMS Alpha Version 7.3-2, you must also install new versions of DECwindows and DECnet-Plus. One of the reasons that makes this necessary is a change of behavior in AUTOGEN (see Section 4.2).
Unlike the behavior of previous versions, DECnet-Plus for OpenVMS Version 7.3-2 now provides product information in NEWPARAMS.DAT records, as required by AUTOGEN. AUTOGEN anticipates this change in DECnet-Plus, so AUTOGEN does not print any warnings when it removes "bad" records from CLU$PARAMS.DAT; AUTOGEN presumes these records were made by an older DECnet-Plus kit and will be replaced by the new DECnet-Plus kit. So, under normal conditions, you will not see any striking differences in behavior during an OpenVMS Version 7.3-2 installation or upgrade.
However, if other products do not provide product information in NEWPARAMS.DAT records, as now required by AUTOGEN, AUTOGEN prints warning messages to both the report and the user's SYS$OUTPUT device. The warnings state that AUTOGEN cannot accept the parameter assignment found in NEWPARAMS.DAT (because no product name is attached) and that no records will be added to CLU$PARAMS.DAT. Since no records are added, the expected additions or other alterations to SYSGEN parameters will not be made, which could lead to resource exhaustion. Developers and testers of software products should be aware of this requirement; it may also be of interest to system managers.
This new behavior is intended to protect both the users and providers of layered products. By keeping this information ordered properly so that it can be updated properly, problems resulting from bad updates should be minimized.
A description of NEWPARAMS.DAT and CLU$PARAMS.DAT is included in the
AUTOGEN chapter of the HP OpenVMS System Management Utilities Reference Manual.
If you upgrade to OpenVMS Version 7.3 or higher and your system has either DCE for OpenVMS or DECnet-Plus for OpenVMS installed on it, when you install DECnet-Plus you may get PCSI-I-RETAIN informational messages for the following files:
You can ignore these messages. The DECnet-Plus kit has been properly
These notes pertain to HP PATHWORKS and HP Advanced Server for OpenVMS
products, and include information about installing or upgrading OpenVMS
systems running these products.
Version 7.3A of Advanced Server for OpenVMS is supported on OpenVMS
Alpha Version 7.3-1 and higher systems. Advanced Server Versions 7.2
and 7.2A for OpenVMS servers must be upgraded. For more information
about upgrading Advanced Server for OpenVMS servers, see Section 184.108.40.206.
Version 6.1 of PATHWORKS for OpenVMS (Advanced Server) is supported on
OpenVMS Alpha Version 7.3-1 and higher systems. Earlier versions of
PATHWORKS for OpenVMS servers must be upgraded. For more information
about upgrading earlier versions of PATHWORKS, see Section 220.127.116.11.
PATHWORKS V5 for OpenVMS (LAN Manager) is not supported on OpenVMS Version 7.3-2.
If you are running PATHWORKS V5 for OpenVMS (LAN Manager) and you want to offer file and print services on OpenVMS Version 7.3-2, you must upgrade the file and print server to PATHWORKS V6.1 for OpenVMS (Advanced Server) before you install OpenVMS Version 7.3-2.
You cannot upgrade directly from PATHWORKS V5 for OpenVMS (LAN Manager)
to Advanced Server V7.3x for OpenVMS. For information about
upgrading from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS
V6.x for OpenVMS (Advanced Server), refer to the PATHWORKS
for OpenVMS (Advanced Server) Server Installation and Configuration
Guide provided with the kit documentation. For information about
upgrading earlier versions of PATHWORKS for OpenVMS (Advanced Server)
to PATHWORKS V6.1 for OpenVMS (Advanced Server), see Section 18.104.22.168.
If you are upgrading an OpenVMS system that is currently running a version of PATHWORKS for OpenVMS (Advanced Server) that is earlier than Version 6.1, follow these steps:
22.214.171.124 Upgrading Advanced Server Version 7.2x for OpenVMS
If you you want to upgrade your Advanced Server for OpenVMS server, follow these steps:
Customers with HP X.25 for OpenVMS Alpha systems software must upgrade to X.25 Version 1.6 prior to upgrading to OpenVMS 7.3-1 or higher. Failure to upgrade will result in system failures with an SPLINVIPL bugcheck when booting.
HP also recommends that you install the latest X.25 ECO kit, which is named X25ALP X25_V16ECO1 X.25 V1.6 for OpenVMS Alpha. This ECO kit contains two separate kits, one for X.25 and one for WANDD, which are named as follows:
You can access the X25_V16ECO1 kit from the following website if you are a contract customer and already have an account:
If you are not already a contract customer or if you do not have an
account at the patch site, you can create an account at this site or
contact a customer service representative to obtain the kit.
If you installed Kerberos Version 1.0 for OpenVMS using a POLYCENTER Software Installation kit, you must use the POLYCENTER Software Installation utility to remove Kerberos Version 1.0 before you upgrade the operating system. (You do not need to remove Kerberos if you are running Version 2.0 or if Version 1.0 was installed as part of the OpenVMS Version 7.3-1 operating system.)
To remove Kerberos, choose Option 6 "Remove installed products" from the installation CD main menu. During the removal, you are asked whether you want to remove the data and directories. (Data refers to the configuration data files along with the principal database, if one was created.) If you want to save this information for use later, respond "No" to the question. Return to the main menu and perform the upgrade of OpenVMS.
After the upgrade, the new Kerberos directories are located in KRB$ROOT:[*...]. (KRB$ROOT is defined as a system-wide logical name when Kerberos is started.) Kerberos data is either created during configuration or moved from the old Kerberos directories and renamed. If you removed a previously installed Kerberos kit and saved the data and directories, the data will automatically be moved into the new directories and be renamed the first time the Kerberos startup procedure is run after the upgrade.
Start the Kerberos servers by entering the following command:
Note that the Kerberos startup procedure moves and renames only known Kerberos files. Users who have created files in the old Kerberos directories must manually move those files.
For more information about installing and configuring Kerberos, refer
to HP Open Source Security for OpenVMS, Volume 3: Kerberos.
The Registry that shipped with OpenVMS Alpha Version 7.2-1 and Version 7.2-1H1 is different from and incompatible with the Registry that ships with Versions 7.2-2 and higher. If you are upgrading from an earlier version with the old Registry, you must take special steps, depending on what you want to do.
The following steps describe the procedure you can use when upgrading from Version 7.2-1 or from 7.2-1H1 to Version 7.2-2 or higher on systems running the OpenVMS NT Registry: