OpenVMS Version 7.3 Release Notes
OpenVMS Version 7.3 Release Notes
Order Number:
AA--QSBTD--TE
June 2001
This manual describes changes to the software; installation, upgrade,
and compatibility information; new and existing software problems and
restrictions; and software and documentation corrections.
Note
This online version of the release notes manual has the most current
information compared to the printed version of this manual.
|
Revision/Update Information:
This is a new manual.
Software Version:
OpenVMS Alpha Version 7.3
OpenVMS VAX Version 7.3
Compaq Computer Corporation
Houston, Texas
© 2001 Compaq Computer Corporation
Compaq, AlphaServer, POLYCENTER, VAX, VMS, and the Compaq logo
Registered in U.S. Patent and Trademark Office.
OpenVMS and Tru64 are trademarks of Compaq Information Technologies
Group, L.P. in the United States and other countries.
Motif, OSF1, and UNIX are trademarks of The Open Group in the United
States and other countries.
PostScript is a trademark of Adobe Systems, Inc.
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.
ZK6637
The Compaq OpenVMS documentation set is available on CD-ROM.
Preface
Intended Audience
This manual is intended for all OpenVMS operating system users. Read
this manual before you install, upgrade, or use Version 7.3 of the
operating system.
Document Structure
This manual contains the following chapters and appendixes:
- Chapter 1 contains information describing the type of OpenVMS
releases, upgrade paths, and support policy.
- Chapter 2 contains release notes that pertain to installing the
OpenVMS operating system.
- Chapter 3 contains installation and support information about
OpenVMS associated products.
- Chapter 4 contains release notes about the general use of the
OpenVMS operating system.
- Chapter 5 contains release notes specific to system management
issues.
- Chapter 6 contains release notes that relate to programming on an
OpenVMS system, including notes for compilers, linkers, and run-time
library routines.
- Chapter 7 contains release notes pertaining to OpenVMS device
support on Alpha and VAX systems.
- Chapter 8 describes the proper use of interlocked memory
instructions, which is crucial for the Alpha 21264 (EV6) processor.
- Appendix A contains information about OpenVMS 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 operating system.
In Chapters 2 through 8, notes are organized by facility or product
name; facilities and products are listed alphabetically.
This manual contains release notes introduced in the current release
and notes from previous OpenVMS versions that still apply to the new
release. Margin notes for each release note indicate 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.
Related Documents
For a list of additional documents that are available in support of
this version of the OpenVMS operating system, refer to the OpenVMS Version 7.3 New Features and Documentation Overview.
For additional information about OpenVMS products and services, access
the following Compaq web site:
http://h18000.www1.hp.com/openvms/
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
Use the following World Wide Web address to order additional
documentation:
http://h18000.www1.hp.com/openvms/
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 Introduction
This chapter contains information about the following topics:
- OpenVMS releases
- Upgrade paths
- Support policy
1.1 OpenVMS Releases
The following sections describe the differences in OpenVMS releases.
Full upward compatibility of user-mode code is part of any OpenVMS
release.
1.1.1 OpenVMS Major Release
The purpose of a major release is to identify to our customers and
application providers that we are providing significant new features,
particularly changes to kernel interfaces and kernel-mode data
structures. These changes may require the recoding or recompilation of
applications that use these privileged-mode interfaces. Full upward
compatibility of user-mode code is expected.
An example of a major release is OpenVMS Alpha Version 6.0 or OpenVMS
Version 7.0. Major releases are sometimes referred to as
point-zero releases.
Major releases are shipped to all customers with the appropriate
software service contracts.
1.1.2 OpenVMS New Feature Release
The purpose of a new feature release is to provide new features, as
well as enhancements to existing features and maintenance updates.
These changes do not generally require recoding or recompiling of
privileged-mode applications. Full upward compatibility of user-mode
code is expected.
An example of a new feature release is OpenVMS VAX Version 6.2 or
OpenVMS Alpha Version 7.3. New feature releases are sometimes referred
to as point releases.
New feature releases are shipped to all customers with the appropriate
software service contracts.
1.1.3 OpenVMS Minor Release
The purpose of a minor release is to provide some new features,
enhancements to existing features, new hardware and option support, and
maintenance for the previous release. Minor releases are not expected
to have any impact on applications. Full upward compatibility of
user-mode code is expected.
An example of a minor release is OpenVMS Alpha Version 7.2-1 or OpenVMS
VAX Version 5.5-2. Minor releases are sometimes referred to as
dash releases.
Minor releases are shipped to all customers with the appropriate
software service contracts.
1.1.4 OpenVMS Limited Hardware Release
Limited hardware releases are specific to, tested for, and targeted at
new systems, new option support, and new hardware configurations.
These releases may include specific remedial fixes that are required to
support the new hardware, but they do not include enhancements or
general maintenance. No application impact is expected. Full upward
compatibility of user-mode code is expected.
Limited hardware releases are ordered explicitly by customers and are
not automatically shipped to customers with software service contracts.
A customer receives the limited hardware release when they acquire new
systems, new options, or new configurations.
An example of a limited hardware release is OpenVMS Alpha Version
7.2-1H1 or OpenVMS VAX Version 5.5-2H4.
1.2 Upgrade Paths
The following figures show the upgrade and rolling upgrade paths for
OpenVMS Alpha and OpenVMS VAX.
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. You must have more than one system
disk. The systems that are not being upgraded remain available.
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.
The red lines in Figure 1-1 and Figure 1-2 indicate direct
supported upgrade paths to Version 7.3. All other lines indicate
supported upgrade paths, some for prior versions.
OpenVMS Alpha
Figure 1-1 illustrates the OpenVMS Alpha upgrade paths. The red lines
indicate the direct upgrade paths to Version 7.3.
Figure 1-1 OpenVMS Alpha Upgrade Paths
For OpenVMS Alpha, you can upgrade directly to Version 7.3 from Version
6.2x, Version 7.0, Version 7.1x, and 7.2x.
Cluster rolling upgrades are supported from Version 7.1-2 and Version
7.2x.
For complete instructions on installing or upgrading to OpenVMS Alpha
Version 7.3, refer to the OpenVMS Alpha Version 7.3 Upgrade and
Installation Manual.
OpenVMS VAX
Figure 1-2 illustrates the OpenVMS VAX upgrade paths. The red lines
indicate the direct upgrade paths to Version 7.3.
Figure 1-2 OpenVMS VAX Upgrade Paths
For OpenVMS VAX, you can upgrade directly to Version 7.3 from Version
6.1, Version 6.2, Version 7.0, Version 7.1, and Version 7.2.
If you are running Version 5.5-2, you can upgrade to Version 6.1 and
then to Version 7.3.
Caution
Install the following remedial kit before upgrading from Version 6.1 to
Version 7.3.
|
Remedial kits can be accessed at the following World Wide Web (WWW)
address:
http://h18000.www1.hp.com/support/
If you have a service contract and cannot download software from the
Internet, call your Compaq support representative to receive the
remedial kit on media appropriate for your system.
Cluster rolling upgrades are supported from Version 7.1 and Version 7.2.
For complete instructions on installing or upgrading to OpenVMS VAX
Version 7.3, refer to the OpenVMS Alpha Version 7.3 Upgrade and
Installation Manual.
1.3 Upgrade and Installation Documentation Correction
V7.3
The warranted and migration support information in the printed version
of the OpenVMS Alpha and VAX Upgrade and Installation Manuals is
incorrect. Please use the corrected information in the following table
or refer to the OpenVMS Version 7.3 New Features and Documentation Overview.
Compaq provides two levels of support, warranted and migration, for
mixed-version and mixed-architecture OpenVMS Cluster systems.
Compaq supports only two versions of OpenVMS running in a cluster at
the same time, regardless of architecture. Migration support helps
customers move to warranted OpenVMS Cluster version mixes with minimal
impact on their cluster environments.
Table 1-1 shows the level of support provided for all possible
version pairings.
1.4 Compaq's Support Policy
V7.3
Compaq provides support for the current version and the previous
version (for up to 12 months) of the OpenVMS operating system. For
earlier software versions, a Prior Version Support contract may be
available.
A software release is considered a current version when it is the most
recent release and for the twelve months following the release of a
subsequent version. A subsequent version is defined as a Major or New
Feature release. Major releases contain substantial new functionality.
The version number increases to the next integer (for example, 6.2 to
7.0). New Feature releases contain some additional functionality. The
version number increases to the next decimal fraction (for example, 7.2
to 7.3). Thereafter, Prior Version Support may be available.
For information about all levels of support, contact your Compaq
support representative or access the following Compaq web site:
http://h18000.www1.hp.com/support/
For information about Prior Version Support services, access the
following Compaq web sites:
http://h18000.www1.hp.com/services/software/ss_mature.html
http://h18000.www1.hp.com/services/software/ss_pvs.html
|