HP OpenVMS Systems Documentation

Content starts here

HP OpenVMS Version 8.3 Release Notes

Previous Contents

Chapter 1
OpenVMS Software Installation and Upgrade Release Notes

This chapter contains information that you need to know before installing or upgrading to OpenVMS Version 8.3. Topics of interest to both Alpha and I64 users are covered first. Later sections group notes of interest to users of specific platforms.

HP recommends that you read all of the following manuals before installing or upgrading OpenVMS Version 8.3:

  • HP OpenVMS Version 8.3 Release Notes (this manual)
  • HP OpenVMS Version 8.3 New Features and Documentation Overview
  • HP OpenVMS Version 8.3 Upgrade and Installation Manual

Refer to Chapter 6 for hardware release notes and to Chapter 2 for information about associated products.

1.1 HP Software Technical Support Policy

HP provides software technical support for OpenVMS operating system software for the latest, currently shipping version and the immediate prior version of the product. Each version is supported for 24 months from its release date, or until the release of the second subsequent version, whichever is greater. "Version" is defined as a release containing new features and enhancements. Patch kits and maintenance-only releases do not meet the definition of "version" in the context of this support policy.

Current version-level support (Standard Support or SS) and Prior Version Support (PVS) for OpenVMS operating system software is provided for OpenVMS versions in accordance with these guidelines. The current level of support for recent versions of OpenVMS Alpha and OpenVMS VAX is kept up to date on this web page:


The Operating System Support Policy applies to all OpenVMS Major Releases, New Feature Releases, and Enhancement releases, which are defined as follows:

  • Major Releases for OpenVMS contain substantial new functionality. The version number increases to the next integer (for example, from 6.2-1H1 to 7.0).
    Application impact: OpenVMS internal interfaces have changed. Although binary compatibility will be maintained for the majority of applications, independent software vendors (ISVs) should test on the new version and may need to release a new application kit. Some application partners may want to release a new application kit to take advantage of new features in the operating system.
  • New Feature Releases for OpenVMS contain new features, enhancements, and maintenance updates. The version number increases to the next decimal number (for example, from 7.2 to 7.3).
    Application impact: The release has not retired any published application programming interfaces (APIs). However, OpenVMS internal interfaces may have been modified with the addition of significant new functionality or implementation of performance improvements. It is unlikely that a new application kit will be required for 95 percent of all applications that use documented APIs. Device driver and kernel-level applications (that is, those that use nonstandard or undocumented APIs) may need qualification testing.
  • Enhancement Releases for OpenVMS contain enhancements to existing features and maintenance updates. The version number increases to show a revision by using a dash (for example, OpenVMS Version 7.3-2).
    Application impact: The release may contain new hardware support, software enhancements, and maintenance, but the changes are isolated and have no impact on applications that use published APIs. There is no need for ISVs to test on the new release or to produce a new application kit.
  • Hardware Releases provide current version-level support until 12 months after a subsequent release containing that particular hardware support. Hardware releases are shipped with new hardware sales only and are not distributed to existing service customers.

The following OpenVMS core products are supported at the same level (Standard Support or Prior Version Support) and duration as the operating system version on which they ship:

  • HP Advanced Server for OpenVMS
  • HP DECnet (Phase IV)
  • HP DECnet-Plus for OpenVMS
  • HP OpenVMS Cluster Client Software
  • HP OpenVMS Cluster Software for OpenVMS
  • HP PathWorks or HP PATHWORKS for OpenVMS
  • HP RMS Journaling for OpenVMS
  • HP TCP/IP Services for OpenVMS
  • HP Volume Shadowing for OpenVMS
  • HP DECram for OpenVMS

These products require their own individual support contracts and are not included in the operating system support contract.

1.2 General Application Compatibility Statement

OpenVMS has consistently held the policy that published APIs are supported on all subsequent releases. It is unlikely applications that use published APIs will require changes to support a new release of OpenVMS. APIs may be "retired," and thus removed from the documentation; however, the API will continue to be available on OpenVMS as an undocumented interface.

1.3 Obtaining Remedial Kits

Remedial kits for HP products are available online at the HP IT Resource Center (ITRC). Use of the ITRC patch download site requires user registration and login. Registration is open to all users and no service contract is required. You can register and log in from the following URL:


You can also use FTP to access patches from the following location:


1.4 Networking Options


OpenVMS provides customers with the flexibility to choose the network protocol of their choice. Whether you require DECnet or TCP/IP, OpenVMS allows you to choose the protocol or combination of protocols that works best for your network. OpenVMS can operate with both HP and third-party networking products.

During the main installation procedure for OpenVMS Version 8.3, you have the option of installing the following supported HP networking software:

  • Either HP DECnet-Plus Version 8.3 for OpenVMS or HP DECnet Phase IV Version 8.3 for OpenVMS. (Note that both DECnet products cannot run concurrently on your system.)
    DECnet-Plus contains all the functionality of the DECnet Phase IV product, plus the ability to run DECnet over TCP/IP or OSI protocols.

Alternatively, after you install OpenVMS, you can install your choice of another third-party networking product that runs on OpenVMS Version 8.3.

For information about how to configure and manage your HP networking software after installation, refer to the TCP/IP, DECnet-Plus, or DECnet documentation. The manuals are available in online format on the OpenVMS Documentation CD; printed manuals can be ordered from HP (800-282-6672).

HP strongly recommends that you apply the current Engineering Change Order (ECO) for TCP/IP Services for OpenVMS Version 5.5 after upgrading to OpenVMS Version 8.2--1 to ensure that the latest software is installed.

1.5 Disk Incompatibility with Older Versions of OpenVMS


The OpenVMS Version 8.3 installation procedure initializes the target disk with volume expansion (INITIALIZE/LIMIT). This renders the disk incompatible with versions of OpenVMS prior to Version 7.2. In most cases, this does not present a problem. However, if you intend to mount this new disk on a version of OpenVMS prior to Version 7.2, you must first take steps to make the disk compatible for that operating system version. Refer to the HP OpenVMS Version 8.3 Upgrade and Installation Manual for detailed instructions.

Note that by taking these steps, your new system disk might include a relatively large minimum allocation size (as defined by /CLUSTER_SIZE). As a result, small files will use more space than necessary. Therefore, you should perform these steps only for system disks that must be mounted on versions of OpenVMS prior to Version 7.2.


ODS-5 disks are also incompatible with versions of OpenVMS prior to Version 7.2.

1.6 HP DECwindows Motif for OpenVMS


The following table lists which versions of DECwindows Motif are supported on various platforms of the OpenVMS Version 8.3 operating system.

Table 1-1 Supported Versions of DECwindows Motif
OpenVMS Version DECwindows Motif Version
OpenVMS I64 8.3 DECwindows Motif for OpenVMS I64 V1.5
OpenVMS Alpha 8.3 DECwindows Motif for OpenVMS Alpha V1.5

The DECwindows Motif software relies on specific versions of OpenVMS server and device driver images. Be sure to install or upgrade to the version of DECwindows Motif that is appropriate to your operating system environment, as noted in Table 1-1.

For information on support for prior versions of DECwindows Motif, see the HP DECwindows Motif for OpenVMS Release Notes.

For detailed information about installing the DECwindows Motif software, refer to the HP DECwindows Motif for OpenVMS Installation Guide.

1.7 Release Notes for OpenVMS for Integrity Servers Users

The following notes are primarily of interest to users of OpenVMS for Integrity servers.

1.7.1 A6825A Gigabit Ethernet Controller and RX4640 Restriction V8.3


The HP sx1000 Chipset for HP Integrity servers provides the CPU, memory, and I/O subsystem to the HP Integrity rx7620, HP Integrity 8620, and HP Integrity Superdome servers. The cell controller is combined with four CPU chips into the computing cell in the sx1000 Chipset architecture. The cell controller chip also provides paths to the I/O devices and off-cell memory.

The rx7620, rx8620, and Superdome servers provide a varying number of sx1000 Chipset cells. The rx7620 provides up to 2 cells (8 CPUs), the rx8620 provides up to 4 cells (16 CPUs), and the Superdome provides up to 16 cells (64 CPUs).

For OpenVMS I64 Version 8.3, there are two primary storage interconnects:

  • The SCSI storage type is U320, used for core I/O for certain Integrity server systems, as well as the A7173A U320 SCSI adapter. For connection to external SCSI storage, the supported storage shelves are the DS2100 or the MSA30.
  • The external Fibre Channel storage connection is through the dual-port 2GB Fibre Channel Universal PCI-X adapter (A6826A). This adapter allows for connectivity to any external SAN-based Fibre Channel storage infrastructure supported by OpenVMS.

Customers who used any earlier evaluation or field test kits should note the following important considerations:

  • In the SCSI adapter area, the U160 adapter (A6829A) is not officially supported on OpenVMS I64 Version 8.3, and reached end-of-life in 2005. However, you can use this adapter for existing hardware configurations as long as the system remains as it is currently configured. Any additional adapters, or movement to another server, require the U320 SCSI adapter technology.
  • In the case of Fibre Channel, customers might have been running with the AB232A or KGPSA-EA FC adapters. These adapters are not supported on OpenVMS I64 Version 8.3, and customers using them must upgrade to the A6826A FC adapter before running production applications on Version 8.2.

1.7.2 UI60 SCSI Support on the rx7620 and rx8620


The rx7620 and rx8620 have an internal U160 (SCSI) that comes with the system as core I/O. The internal connections to the racks of SCSI disks (which appear on the front of the system box) are supported by OpenVMS. The internal box also has two external ports. HP does not support attaching them (via cables) to a SCSI rack.

1.7.3 Clearing the System Event Log (SEL) on Integrity Servers


HP Integrity servers maintain a System Event Log (SEL) within system console storage, and OpenVMS I64 automatically transfers the contents of the SEL into the OpenVMS error log. If you are operating from the console during a successful boot operation, you might see a message indicating that the Baseboard Management Controller (BMC) SEL is full. You can safely continue when the BMC SEL is full by following the prompts; OpenVMS will process the contents of the SEL. If you wish to clear the SEL manually, enter the following command at the EFI Shell prompt:

Shell> clearlogs SEL

This command deletes the contents of the SEL. The command is available with current system firmware versions.

If your Integrity server is configured with a Management Processor (MP) and you see a BMC event log warning while connected to the MP console, you can clear the BMC event log by using MP. Press Ctrl/B to drop to the MP> prompt. At the MP> prompt, enter SL (from the main menu) and use the C option to clear the log.

HP recommends that you load and use the most current system firmware. For more information about updating the system firmware, refer to the HP OpenVMS Version 8.3 Upgrade and Installation Manual.

1.7.4 Firmware for Integrity Servers


OpenVMS I64 Version 8.3 was tested with the latest firmware for each of the supported Integrity servers. The following table lists the recommended firmware versions:

Table 1-2 Firmware Versions for Entry-Class Integrity Servers
System System
rx1600 2.18 3.48 E.03.15 N/A
rx1620 2.18 3.48 E.03.15 N/A
rx2600 2.31 1.53 E.03.15 N/A
rx2620 3.17 3.47 E.03.15 N/A
rx4640 3.17 3.49 E.03.15 1.10

Some new rx4640 servers require, and will ship with, the higher firmware versions shown in the table. As this manual goes to press, the lower firmware versions are the latest released to customers to update existing servers. OpenVMS has been tested with both versions of firmware. HP recommends that all rx4640 servers be updated to the higher firmware versions when the firmware is released.

To check the firmware versions for your server, use the Extensible Firmware Interface (EFI) command INFO FW, as shown in the following example. (For instructions on how to access and use EFI, refer to the HP OpenVMS Version 8.3 Upgrade and Installation Manual.)

Shell> INFO FW


   Firmware Revision: 2.13 [4412]          (1)

   PAL_A Revision: 7.31/5.37
   PAL_B Revision: 5.65
   HI Revision: 1.02

   SAL Spec Revision: 3.01
   SAL_A Revision: 2.00
   SAL_B Revision: 2.13

   EFI Spec Revision: 1.10
   EFI Intel Drop Revision: 14.61
   EFI Build Revision: 2.10

   POSSE Revision: 0.10

   ACPI Revision: 7.00

   BMC Revision: 2.35                       (2)
   IPMI Revision: 1.00
   SMBIOS Revision: 2.3.2a
   Management Processor Revision: E.02.29   (3)

  1. The system firmware revision is 2.13.
  2. The BMC firmware revision is 2.35.
  3. The MP firmware revision is E.02.29.

The HP Integrity rx4640 server contains Dual Hot Plug Controller (DHPC) hardware with upgradable firmware. To check the current version of your DHPC firmware, use the EFI command INFO CHIPREV, as shown in the following example. The hot-plug controller version will be displayed. A display of 0100 indicates version 1.0; a display of 0110 means version 1.1.



   Chip                  Logical     Device       Chip
   Type                     ID         ID       Revision
   -------------------   -------     ------     --------
   Memory Controller         0       122b         0023
   Root Bridge               0       1229         0023
     Host Bridge          0000       122e         0032
     Host Bridge          0001       122e         0032
     Host Bridge          0002       122e         0032
     Host Bridge          0004       122e         0032
      HotPlug Controller     0          0         0110
     Host Bridge          0005       122e         0032
      HotPlug Controller     0          0         0110
     Host Bridge          0006       122e         0032
     Other Bridge            0          0         0002
       Other Bridge          0          0         0008
         Baseboard MC        0          0         0235

For instructions on upgrading your firmware, refer to the HP OpenVMS Version 8.3 Upgrade and Installation Manual.

1.7.5 Booting from the Installation DVD


On I64 systems with the minimum amount of supported memory (512MB), the following message appears when booting from the installation DVD:

********* XFC-W-MemmgtInit Misconfigure Detected ********
XFC-E-MemMisconfigure MPW_HILIM + FREEGOAL > Physical Memory and no reserved memory for XFC
XFC-I-RECONFIG Setting MPW$GL_HILIM to no more than 25% of physical memory XFC-I-RECONFIG
Setting FREEGOAL to no more than 10% of physical memory
********* XFC-W-MemMisconfigure AUTOGEN should be run to correct configuration ********
********* XFC-I-MemmgtInit Bootstrap continuing ********

The message means that the system cache (XFC) initialization has successfully adjusted the SYSGEN parameters MPW_HILIM and FREEGOAL to allow caching to be effective during the installation. You can continue with the installation.

1.7.6 HP DECwindows Motif Release Notes

The following DECwindows Motif release notes are of interest to OpenVMS I64 users. Keyboard Support


The only model keyboard supported on HP DECwindows Motif for OpenVMS I64 systems is the LK463 (AB552A for I64) keyboard. Although other types of keyboards may function in the OpenVMS I64 environment, HP does not currently support them. Connect Peripheral Devices Prior to Server Startup


To properly configure your system as a DECwindows X display server, you must have all the following peripheral components connected prior to startup:

  • monitor
  • USB mouse
  • USB keyboard

Otherwise, the server system might not complete the device initialization process correctly. For example, starting up a server system without input devices (mouse and keyboard) could result in a blank screen.

To correct this problem, disconnect and reconnect all peripherals. Countdown Messages Displayed During Startup


When running DECwindows Motif in client-only mode (with no server configured), messages similar to the following might be displayed during startup:

Waiting for mouse...
Waiting for keyboard...

These messages indicate that device polling is underway and are informational only. They will disappear once the 15-second countdown is complete.

To prevent the messages from displaying, connect the input devices (USB mouse and USB keyboard) to the system prior to startup.

1.8 Release Notes for OpenVMS Alpha Users

The following notes are primarily of interest to users of OpenVMS Alpha systems.

1.8.1 Firmware for OpenVMS Alpha Version 8.3


OpenVMS Alpha Version 8.3 was tested with the platform-specific firmware included on Alpha Systems Firmware CD Version 6.8. For older platforms no longer included on the Firmware CD, OpenVMS Alpha Version 8.2 was tested with the latest released firmware version. HP recommends upgrading to the latest firmware before upgrading OpenVMS.

The OpenVMS Alpha Version 8.3 kit includes the Alpha Systems Firmware CD-ROM and Release Notes. Read the firwmware Release Notes before installing the firmware.

You can obtain Version 6.8 and the latest firmware information from the following website (URL is case sensitive):


1.8.2 Upgrade Paths


You can upgrade directly to OpenVMS Alpha Version 8.3 from only the following versions of OpenVMS Alpha.

For Alpha:

Version 7.3-2 to V8.3
Version 8.2 to V8.3

For I64:

Version 8.2 to V8.3
Version 8.2-1 to V8.3

If you are currently running OpenVMS Alpha Version 6.2x through 7.3, inclusive, you must first upgrade to Version 7.3-2, and then to Version 8.3. Note that standard support for OpenVMS Alpha Version 7.3-1 systems ended on March 31, 2005. After that, OpenVMS Alpha V7.3-1 systems will not be under Prior Version Support (PVS). For details about OpenVMS operating system support, see the chart on the following website:


If you are running other versions of OpenVMS that are no longer supported, you must do multiple upgrades in accordance with upgrade paths that were documented for earlier versions.

Cluster Concurrent Upgrades

During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk. No one can use the cluster until you upgrade and reboot each computer. Once you reboot, each computer will be running the upgraded version of the operating system.

Cluster Rolling Upgrades

During a cluster rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster (a mixed-version cluster). There must be more than one system disk. The systems that are not being upgraded remain available.

Only the following OpenVMS Alpha and OpenVMS VAX versions are supported in mixed-version clusters that include OpenVMS Alpha Version 8.3:

Version 7.3-2 (Alpha)
Version 7.3 (VAX)

If you are upgrading in a cluster environment, rolling upgrades are supported from Version 7.3-2 and 7.3-1 of the OpenVMS Alpha operating system. If you have other versions in a cluster, you cannot do a rolling upgrade until those versions are upgraded to a supported version.

Mixed-version support for all of these versions requires the installation of one or more remedial kits. For more information, see Section 4.14.1.


HP currently supports only two versions of OpenVMS (regardless of architecture) running in a cluster at the same time. Only two architectures are supported in the same OpenVMS Cluster. Warranted support is provided for pairings with OpenVMS I64 Version 8.3. For more information, refer to the HP OpenVMS Version 8.3 Upgrade and Installation Manual.

For a discussion of warranted pairs and migration pairs of OpenVMS operating systems, for complete instructions for installing or upgrading to OpenVMS Alpha Version 8.3, and for instructions on installing OpenVMS I64 Version 8.3, refer to the HP OpenVMS Version 8.3 Upgrade and Installation Manual.

1.9 CDSA: Secure Delivery Signing for Third Parties Available After Release of OpenVMS V8.3


CDSA Version 2.2, which is included with OpenVMS Version 8.3, will allow for organizations other than OpenVMS Engineering to sign and validate OpenVMS kits using the new OpenVMS Secure Delivery functionality. Although the capability to sign and validate kits is included with CDSA Version 2.2, the supporting business practices are not currently in place to support third party vendors signing their own kits. HP expects to allow third party signing soon. Please monitor the HP Developer & Solution Partner Program web site (http://www.hp.com/dspp) for announcements about the availability of this program.

1.10 Remove Any Lines from SYS$MANAGER:SYSTARTUP_VMS.COM That Start Encrypt or SSL


The startup command procedures for Encrypt and SSL are now called from the VMS$LPBEGIN-050_STARTUP.COM procedure. If you are upgrading from a previous version of OpenVMS that had these products installed, edit SYSTARTUP_VMS.COM to remove the calls to SYS$STARTUP:ENCRYPT_START.COM and SYS$STARTUP:SSL$STARTUP.COM. This will prevent these command procedures from executing twice.

1.11 Kerberos for OpenVMS


Before configuring or starting Kerberos, check the HP TCP/IP local host database to determine whether your hostname definition is the short name (for example, node1) or the fully qualified domain name (FQDN) (for example, node1.hp.com).

If your host name definition is the short name, you must run TCPIP$CONFIG to change the definition to the fully qualified name.

The following example shows that the hostname is the short name:


     LOCAL database

Host address    Host name  node1

The following log is an example of how to change the host name definition to the FQDN.


                TCP/IP Network Configuration Procedure

        This procedure helps you define the parameters required
        to run HP TCP/IP Services for OpenVMS on this system.

        Checking TCP/IP Services for OpenVMS configuration database files.

        HP TCP/IP Services for OpenVMS Configuration Menu

        Configuration options:

                 1  -  Core environment
                 2  -  Client components
                 3  -  Server components
                 4  -  Optional components

                 5  -  Shutdown HP TCP/IP Services for OpenVMS
                 6  -  Startup HP TCP/IP Services for OpenVMS
                 7  -  Run tests

                 A  -  Configure options 1 - 4
                [E] -  Exit configuration procedure

Enter configuration option: 1

        HP TCP/IP Services for OpenVMS Core Environment Configuration Menu

        Configuration options:

                 1  -  Domain
                 2  -  Interfaces
                 3  -  Routing
                 4  -  BIND Resolver
                 5  -  Time Zone

                 A  -  Configure options 1 - 5
                [E] -  Exit menu

Enter configuration option: 2

      HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu

 Hostname Details: Configured=node1, Active=node1

 Configuration options:

   1  -  WE0 Menu (EWA0: TwistedPair 1000mbps)
   2  -    node1                Configured,Active

   3  -  IE0 Menu (EIA0: TwistedPair 100mbps)

   I  -  Information about your configuration

  [E] -  Exit menu

Enter configuration option: 2

      HP TCP/IP Services for OpenVMS Address Configuration Menu

      WE0 node1 Configured,Active WE0

 Configuration options:

         1  - Change address
         2  - Set "node1" as the default hostname
         3  - Delete from configuration database
         4  - Remove from live system
         5  - Add standby aliases to configuration database (for failSAFE IP)

        [E] - Exit menu

Enter configuration option: 1

    IPv4 Address may be entered with CIDR bits suffix.
    E.g. For a 16-bit netmask enter

Enter IPv4 Address []:
Enter hostname [node1]: node1.hp.com

Requested configuration:

      Address  :
      Netmask  : (CIDR bits: 21)
      Hostname : node1.hp.com

* Is this correct [YES]:

  "node1" is currently associated with address "".
  Continuing will associate "node1.hp.com" with "".

* Continue [NO]: YES
Deleted host node1 from host database
Added hostname node1.hp.com ( to host database
* Update the address in the configuration database [NO]: YES
Updated address WE0: in configuration database
* Update the active address [NO]: YES
WE0: delete active inet address node1.hp.com
Updated active address to be WE0:

Next, type E three times to exit the TCP/IP Services configuration menus and return to the DCL ($) prompt.

To verify your change, enter the following command:


     LOCAL database

Host address    Host name  node1.hp.com

If you have not previously configured an earlier version of Kerberos on your system, or if you changed your TCP/IP hostname definition to the FQDN as shown above, you must run the Kerberos configuration program before you start Kerberos.

To reconfigure Kerberos, enter the following command:


After you have a valid configuration, start Kerberos with the following command:


For more information, see the Kerberos for OpenVMS Installation Guide and Release Notes.

1.12 Encryption for OpenVMS Installed with the OpenVMS Operating System


When you install or upgrade OpenVMS, Encryption for OpenVMS creates its own ENCRYPT and DECRYPT commands. Encryption for OpenVMS starts automatically (after SSL for OpenVMS, which also starts automatically). For more information about Encryption for OpenVMS, see HP OpenVMS Version 8.3 New Features and Documentation Overview.


With Version 8.3 of OpenVMS, the DCL command DECRAM is removed because it conflicts with the new DECRYPT command (DECRYPT overwrites the default definition of DECRAM, which you might have been using to start DECram). You should update any command procedures that use the DECRAM command so that they use the foreign command style of DCL. For example:


This change affects the use of the DCL command only; all other aspects of the DECram product remain the same. If you have older versions of DECram on your OpenVMS Alpha system, you must remove them before upgrading. See Section 1.13.

1.13 HP DECram V3.n: Remove Before Upgrading


Starting with OpenVMS Alpha and OpenVMS I64 Version 8.2, DECram ships with the OpenVMS operating system as a System Integrated Product (SIP). If you upgrade to Version 8.3 on an OpenVMS Alpha system from OpenVMS Version 7.3-2, you must remove any old versions of DECram. Refer to the HP OpenVMS Version 8.3 Upgrade and Installation Manual for details.

More DECram release notes are included in Section 2.12.

1.14 Converting the LANCP Device Database After Upgrading


When you upgrade to OpenVMS Alpha Version 8.3 from OpenVMS Version 7.3-2, you might also need to convert the LAN device database to the Version 8.3 format if this is not automatically done by LANACP when LANACP is first run after the upgrade.

To convert the database, issue the following LANCP commands to convert the device database and then to stop LANACP so it can be restarted to use the new database:


1.15 DECnet-Plus Requires a New Version


When you install or upgrade to OpenVMS Alpha Version 7.3-2 or later, you must also install a new version of DECnet-Plus. One of the reasons that make this necessary is a change of behavior in AUTOGEN that was introduced in Version 7.3-2.

Unlike the behavior of previous versions, DECnet-Plus for OpenVMS Version 7.3-2 and later 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 or later 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. Because 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.

1.16 SHADOW_MAX_UNIT Default Setting and Memory Usage


This note updates an earlier note that discussed the default settings for this system parameter but did not describe the amount of main memory consumed by the default settings.

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.


SHAD_MAX_UNIT is a static system parameter. In order for a new setting to take effect, you must reboot your system.

Recommendations for SHADOW_MAX_UNIT settings for volume shadowing are discussed in the HP Volume Shadowing for OpenVMS manual.

1.17 TIE Kit Must be Removed Before Upgrade


The Translated Image Environment (TIE) has been integrated into OpenVMS I64 Version 8.2--1. Refer to the HP OpenVMS Systems Migration Software Web site for further information.


If you have installed any version of the Translated Image Environment (TIE) PCSI kit (HP-I64VMS-TIE) on OpenVMS I64 Version 8.2 or Version 8.2-1, you must manually remove the TIE kit before you upgrade to OpenVMS I64 Version 8.3.

Use the following command to remove the TIE product kit:


Do not install the TIE product kit, HP I64VMS TIE V1.0, on OpenVMS I64 Version 8.2-1 or Version 8.3.

1.18 Installation of a Layered Product to an Alternate Device or Directory May Fail


By default the PRODUCT INSTALL command installs a layered product on the system device in the SYS$COMMON directory tree. If you choose to install a layered product to an alternate device or directory using the /DESTINATION=dev:[dir] qualifier (or by defining the logical name PCSI$DESTINATION ), the installation may fail with an error message stating that one of the following files cannot be found: [SYSLIB]DCLTABLES.EXE , [SYSHLP]HELPLIB.HLB , or [SYSLIB]STARLET*.* . If this happens, answer YES to the question, "Do you want to terminate? [YES]," and then retry the installation using the /NORECOVERY_MODE qualifier.

Previous Next Contents