OpenVMS Alpha Version 7.3--1 Release Notes

Document revision date: 31 July 2002

Order Number: AA--RSD0A--TE

June 2002

This manual describes changes to the software; installation, upgrade, and compatibility information; new and existing software problems and restrictions; and software and documentation corrections.

Revision/Update Information: This is a new manual.

Software Version: OpenVMS Alpha Version 7.3-1

Compaq Computer Corporation
Houston, Texas

Compaq, the Compaq logo, ACMS, Alpha, AlphaServer, DECnet, DECwindows, OpenVMS, PATHWORKS, POLYCENTER, Tru64, VAX, VAXcluster, VMS, and the DIGITAL logo are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S. and/or other countries.

Intel is a trademark of Intel Corporation in the U.S. and/or other countries.

Motif, OSF1, UNIX, and X/Open are trademarks of The Open Group in the U.S. and/or other countries.

Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries.

All other product names mentioned herein may be trademarks of their respective companies.

Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.

ZK6652

The Compaq OpenVMS documentation set is available on CD-ROM.

Contents Index

Preface

Intended Audience

This manual is intended for all OpenVMS Alpha operating system users. Read this manual before you install, upgrade, or use Version 7.3-1 of the operating system.

Document Structure

This manual contains the following chapters and appendixes:

Chapter 1 contains release notes that pertain to installing the OpenVMS Alpha operating system.
Chapter 2 contains installation and support information for OpenVMS Alpha associated products.
Chapter 3 contains release notes about the general use of the OpenVMS Alpha operating system.
Chapter 4 contains release notes specific to OpenVMS system management.
Chapter 5 contains release notes that relate to programming on an OpenVMS Alpha system, including notes for compilers, linkers, and run-time library routines.
Chapter 6 contains release notes pertaining to OpenVMS device support on Alpha systems.
Chapter 7 describes the proper use of interlocked memory instructions, which is crucial for the Alpha 21264 (EV6) processor.
Appendix A contains information about OpenVMS Alpha products that are no longer supported as of this release, or that are slated for retirement.
Appendix B contains information pertaining to hardware that runs on the OpenVMS Alpha operating system.

Notes are organized by facility or product name when applicable.

This manual contains release notes introduced in the current release and notes from previous OpenVMS Alpha versions that still apply to the new release. A subheading for each release note indicates the version of origin (for example, V7.3).

Notes from previous releases are published when:

The information in the release note has not been documented in hard copy in any other manual in the OpenVMS documentation set, and the note is still pertinent.
The release note may be pertinent in multiple-version OpenVMS Cluster systems.

Reader's Comments

Compaq welcomes your comments on this manual. Please send comments to either of the following addresses:

Internet openvmsdoc@compaq.com

Mail Compaq Computer Corporation
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How to Order Additional Documentation

Visit the following World Wide Web address for information about how to order additional documentation:

http://www.openvms.compaq.com/

If you need help deciding which documentation best meets your needs, call 800-282-6672.

Conventions

The following conventions are used in this manual:

Ctrl/ x A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.

PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.

[Return] In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)
In the HTML version of this document, this convention appears as brackets, rather than a box.

... A horizontal ellipsis in examples indicates one of the following possibilities:

Additional optional arguments in a statement have been omitted.
The preceding item or items can be repeated one or more times.
Additional parameters, values, or other information can be entered.

.
.
. A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.

( ) In command format descriptions, parentheses indicate that you must enclose the choices in parentheses if you specify more than one.

[ ] In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.

| In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.

{ } In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.

bold text This typeface represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason.

italic text Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).

UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.

Monospace text

Monospace type indicates code examples and interactive screen displays.
In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.

- A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.

numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.

Chapter 1
OpenVMS Alpha Software Installation Release Notes

This chapter contains information that you need to know before installing the OpenVMS Alpha Version 7.3-1 operating system.

Compaq recommends that you read all of the following manuals before installing OpenVMS Alpha Version 7.3-1:

OpenVMS Alpha Version 7.3--1 Release Notes (this manual)
OpenVMS Alpha Version 7.3--1 New Features and Documentation Overview
OpenVMS Alpha Version 7.3--1 Upgrade and Installation Manual

1.1 Upgrade Paths

Direct Upgrade Paths to Version 7.3-1

You can upgrade directly to OpenVMS Alpha Version 7.3-1 from only the following versions of OpenVMS Alpha:

Version 7.3
Version 7.2-2
Version 7.2-1
Version 7.2-1H1
Version 7.2
Version 7.1-2

If you are currently on OpenVMS Alpha Version 6.2x or 7.1, you can do a two-step upgrade: first to Version 7.2-x or 7.3, and then to Version 7.3-1.

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. Upgrade paths are the same as for a direct upgrade.

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. There must be more than one system disk. The systems that are not being upgraded remain available.

Only the following OpenVMS Alpha and VAX versions are supported for mixed-version clusters:

Version 7.3-1 (Alpha)
Version 7.3 (Alpha and VAX)
Version 7.2-2 (Alpha)
Version 7.2-1 (Alpha)
Version 7.2-1H1 (Alpha)
Version 7.2 (VAX)

Mixed-version support for some of these versions is restricted for cluster members running either the Registry server or applications that use the Registry services. See Section 4.26.1.

Mixed-version support for all of these versions requires the installation of one or more remedial kits. See Section 4.22.8.

Only two versions are supported in a cluster at one time.

For a discussion of warranted pairs and migration pairs of OpenVMS operating systems, as well as complete instructions on installing or upgrading to OpenVMS Alpha Version 7.3-1, refer to the OpenVMS Alpha Version 7.3-1 Upgrade and Installation Manual.

1.2 Compaq Operating System Support Policy

V7.3-1

Effective immediately, Compaq Computer Corporation provides Standard Support, also known as current version level support, for its operating system software, OpenVMS and Tru64 UNIX, for the greater of:

24 months from the date the version releases, or
As long as it is the currently shipping version, or
12 months after the release of a subsequent version

This policy applies to major releases, new feature releases, and enhancement releases. It does not apply to hardware releases. The four types of releases are as follows:

Major releases for OpenVMS contain substantial new functionality. The version number increases to the next integer (for example, 6.2-1H1 to 7.0). Purchase of License Subscription service or an update license for the OpenVMS operating system is required. Major releases are shipped to service customers who have a valid service update contract. The application impact is that OpenVMS internal interfaces have changed. Although binary compatibility will be maintained for the majority of applications, ISVs should test on the new version, and might need to release a new application kit. Some application partners might want to release a new application kit that takes 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 fraction (for example, 7.2 to 7.3). Purchase of License Subscription service or an update license for the OpenVMS operating system is required. New feature releases are shipped to service customers who have a valid service update contract. The release has not retired any published APIs. However, OpenVMS internal interfaces might have been modified as significant new functionality was added or performance improvements made. It is unlikely that a new application kit will be required for virtually all (95%) of the applications that use documented APIs. Device driver and kernel-level applications, (that is, those that use nonstandard or undocumented APIs) might 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, 7.3-1). Enhancement releases are shipped to service customers who have a valid service update contract; however, License Subscription service or an update license is not required. The release may contain new hardware support, software enhancements and maintenance, but the changes are isolated and have no impact on applications. Compaq is confident that the new release has 100% binary compatibility with the previous release. If an application compatibility problem is discovered, Compaq will assign the problem a high priority and commit to providing a fix. There is no need for ISVs to test on the new release or produce a new application kit.
Hardware releases are an exception to the operating system support policy described above. They are supported at 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 shipped:

TCP/IP Services for OpenVMS
X.25 for OpenVMS
DECnet (Phase IV)
DECnet-Plus for OpenVMS
PATHWORKS
Advanced Server for OpenVMS
VMScluster Software for OpenVMS
OpenVMS Cluster Client Software
RMS Journaling for OpenVMS
Volume Shadowing for OpenVMS

All other products have current version level support until 12 months after a subsequent release.

For detailed information on OpenVMS operating system support, including definitions of the types of OpenVMS releases, visit the following web site:

http://www.compaq.com/services/software/ss_openvms.html

1.3 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; the API will, however, continue to be available on OpenVMS as an undocumented interface.

1.4 Firmware for OpenVMS Alpha Version 7.3-1

V7.3-1

The OpenVMS Version 7.3-1 CD-ROM package includes the Alpha Systems Firmware Update CD-ROM and Release Notes. We recommend you use the updated firmware with OpenVMS Version 7.3-1. Read the Release Notes before installing the firmware. Access the following web site for the most current firmware and the most up-to-date information on firmware (be sure to type the URL exactly as shown):

http://ftp.digital.com/pub/DEC/Alpha/firmware/

Note

The Alpha Systems Firmware Update Version 6.2 restricts the hot-swap capabilities supported in AlphaServer GS160/320 systems. Hot-swap operations should be avoided on these systems with Version 6.2 firmware. Access the firmware website for the latest firmware and information that will correct this restriction.

The minimum version of Alpha Systems Firmware tested with OpenVMS Alpha Version 7.3-1 is Version 6.1.

1.5 Networking Options

V7.3-1

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 supports both Compaq and third-party networking products.

During the main installation procedure for OpenVMS Version 7.3-1, you have the option of installing the following Compaq networking software:

Compaq TCP/IP Services for OpenVMS
TCP/IP Services and DECnet can run concurrently on your system. Once you have installed Compaq DECnet-Plus for OpenVMS and TCP/IP Services on your system, you can run DECnet applications and OSI applications, or both, over your TCP/IP network. Refer to the DECnet-Plus for OpenVMS Management Guide for more information about running DECnet over TCP/IP (RFC 1859) and OSI over TCP/IP (RFC 1006).
Either DECnet-Plus for OpenVMS or Compaq DECnet for OpenVMS Phase IV 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.
Support for DECnet Phase IV is provided to customers with a Prior Version Support Contract.

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, refer to the TCP/IP, DECnet-Plus, or DECnet documentation. The manuals in online format are available on the OpenVMS Documentation CD-ROM and can be ordered in printed format through Compaq (800-282-6672).

1.6 DECevent Version 3.1 or Higher Required for Certain Systems

V7.3-1

Analyzing Earlier Hardware Platforms

DECevent Version 3.1 or higher is required to analyze hardware error log files on certain supported, earlier-version hardware platforms (for example, the 1200, 8400, GS60, and GS140 platforms).

When you install OpenVMS Version 7.3-1 or 7.3, 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 in this order:

Install OpenVMS Version 7.3-1 or 7.3
Install the DECevent software (included in the DECevent kit on the Compaq System Tools CD-ROM)

Otherwise, when you attempt to use the DIAGNOSE command, you will receive the following system message:

$ DIAGNOSE [parameters] %DIA-E-NOINSTAL, DIAGNOSE has not been installed on this system

Analyzing Later Platforms

Compaq Analyze 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).

Analyzing Both Platforms

If you have both a DECevent-supported platform and Analyze-supported storage devices, you will need both DECevent and Compaq Analyze. To install Compaq Analyze, you must install the WEBES Version 4.0 kit and then the latest Service Pak.

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:

http://www.support.compaq.com/svctools/decevent/

Follow the "Download the documentation" link.

For detailed information about operating system requirements and supported hardware for Compaq Analyze, refer to the WEBES Installation Guide, which is with the other WEBES documentation at the following web site:

http://www.support.compaq.com/svctools/webes/

Follow the "View WEBES documentation" link.

For more information about DECevent, refer to the OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.

Contents

Index

privacy and legal statement

6652PRO.HTML

Internet	openvmsdoc@compaq.com
Mail	Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698

Ctrl/ x	A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
PF1 x	A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.
`[Return]`	In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box.
...	A horizontal ellipsis in examples indicates one of the following possibilities: Additional optional arguments in a statement have been omitted. The preceding item or items can be repeated one or more times. Additional parameters, values, or other information can be entered.
. . .	A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
( )	In command format descriptions, parentheses indicate that you must enclose the choices in parentheses if you specify more than one.
[ ]	In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.
\|	In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.
{ }	In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.
bold text	This typeface represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason.
italic text	Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).
UPPERCASE TEXT	Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
Monospace text	Monospace type indicates code examples and interactive screen displays. In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.
-	A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
numbers	All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.