HP OpenVMS Systems Documentation
OpenVMS Version 7.3 Release Notes
3.9.2 Language Variants Not Available in Some Versions
Language variants are not available for Compaq DECwindows Motif for
OpenVMS Version 1.2-6. The Japanese and German variants are available
for DECwindows Motif Version 1.2-5, and the Hebrew variant is available
for DECwindows Motif Version 1.2-4. Consult your Compaq support
representative for more information.
Users of Process Software MultiNet Version 4.3 (or earlier) who are also using DCE should install the UCXDRIVER-041_a043 (or later) ECO from Process Software.
Refer to the following web site to obtain the most recent patch and any dependencies for you version and/or contact Process Software Technical Support:
3.11 Installing Compaq Open3D on OpenVMS Alpha Version 7.3
During installation of Open3D on OpenVMS Alpha Version 7.3, an older version of the SYS$LOADABLE_IMAGES:SYS$GYCDRIVER.EXE image is installed. Before you install Open3D on OpenVMS Alpha Version 7.3 perform one of the following tasks:
3.12 Pascal (Alpha Only)---Installing Compaq Pascal Version 5.5 After an Upgrade
After upgrading to OpenVMS, you should reinstall Compaq Pascal to produce new versions of STARLET.PAS and other definition files to match the upgraded system.
If you do not reinstall Compaq Pascal after upgrading to OpenVMS, the compiler on your system will still work correctly. However, STARLET.PAS and the other definition files will not contain any new or corrected definitions supplied by the OpenVMS upgrade.
Note that because of changes in OpenVMS, the Compaq Pascal Version 5.5
kit can sometimes go into an infinite loop when it is installed on
OpenVMS Alpha. This problem is solved in Compaq Pascal Version 5.6.
There is a known incompatibility between the PL/I RTL distributed with the OpenVMS operating system and the more recent PL/I RTL owned and distributed by Kednos Corporation. The older version shipped with the OpenVMS operating system may overwrite a newer version. The image in question is SYS$LIBRARY:DPLI$RTLSHR.EXE.
OpenVMS distributes the following version of the file, which can be identified by using the ANALYZE/IMAGE command:
If you perform an ANALYZE/IMAGE command before upgrading to OpenVMS V7.3 and find a newer version of DPLI$RTLSHR.EXE, you either copy it and restore it after the upgrade or reinstall the PL/I kit afterward.
Any questions about DEC PL/I and VAX PL/I should be directed to Kednos Corporation at the following address:
3.14 Compaq Reliable Transaction Router (RTR) License
Reliable Transaction Router (RTR) is fault tolerant transactional
messaging middleware used to implement large, distributed applications
using client/server technology. RTR is no longer licensed as a separate
product but is licensed as part of the OpenVMS product. The RTR
binaries and hardcopy documentation are available separately. For more
information on RTR, see the Reliable Transaction Router V4.0 SPD,
This section contains release notes pertaining to Compaq TCP/IP
Services for OpenVMS and DIGITAL TCP/IP Services for OpenVMS.
New features in TCP/IP Services Version 5.1 include:
For information about upgrading to TCP/IP Services for OpenVMS Version
5.1, see the Compaq TCP/IP Services for OpenVMS Release Notes.
DIGITAL TCP/IP Services for OpenVMS Version 4.2 (UCX) is not supported on OpenVMS Version 7.0 and later releases.
Compaq recommends the following workaround:
After a failed power-cycle or INIT boot startup, enter a BOOT command at the console and press Return.
OpenVMS shutdown and reboot commands will perform as expected.
This automatic boot failure is due to a timing problem and will be
corrected in a future release of the Alpha firmware.
4.2 Booting OpenVMS Version 7.3 on a Personal Workstation with IDE Controllers
If you are using the Compaq Personal Workstation 433au, 500au, and 600au series systems, you can boot OpenVMS Version 7.3 from an IDE CD-ROM if the controller chip is a Cypress PCI Peripheral Controller. You cannot boot OpenVMS on an Compaq Personal Workstation au series system from an IDE CD-ROM with an Intel Saturn I/O (SIO) 82378 chip in your configuration. You must use a SCSI CD-ROM if the Intel SIO chip is present.
To determine which IDE chip you have in your configuration, enter the following SRM console command:
If you see Cypress PCI Peripheral Controller, you can boot OpenVMS.
If you see Intel SIO 82378, you will need to use and boot from
a SCSI CD-ROM.
4.3 COM for OpenVMS (Alpha Only) Not Supported in a Mixed-Version Cluster
Because of changes to the OpenVMS Registry protocol, you cannot run COM for OpenVMS software on OpenVMS Alpha Version 7.3 systems and non-Version 7.3 systems in the same cluster.
If you have a mixed-version OpenVMS Cluster system, you can run COM for OpenVMS only on the OpenVMS Alpha system that is running the OpenVMS Registry server or on other OpenVMS Alpha systems running the same version of OpenVMS as the system running the Registry Server.
For more information about the OpenVMS Registry protocol change, see Section 5.10.
For information about installing and configuring COM for OpenVMS, see
the OpenVMS Connectivity Developer Guide.
4.4 Online Help New and Changed Topics
With Version 7.3, a number of new Help topics have been added and the names of some old Help topics have been changed.
Online Help now includes all the OpenVMS utility routines that are described in the OpenVMS Utility Routines Manual, as follows:
Some of these utility names begin with strings that match the names of previously existing Help topics, so the names of the following older Help topics have been changed to make them unique when you enter a sufficient number of characters:
|Old Topic Name||New Topic Name|
A few more changes and additions have been made to Help topics:
The OpenVMS Version 7.3 CD-ROM package includes the Alpha Systems Firmware Update Version 5.9 CD-ROM and Release Notes. Read the Release Notes before installing the firmware.
Included in the OpenVMS Version 7.3 CD-ROM kit are the OpenVMS Freeware Version 5.0 CD-ROMs. The Freeware CD-ROMs contain free software tools and utilities for creating applications and managing OpenVMS systems.
To mount the Freeware CD-ROMs, insert a CD-ROM into the CD-ROM drive and enter the following commands appropriate to the freeware volume being mounted. For additional information on the freeware, refer to the FREEWARE_README.TXT files.
Freeware CD-ROM 1
$ MOUNT ddcu:FREEWARE50_1 $ TYPE DISK$FREEWARE50_1:$FREEWARE_README.TXT
Freeware CD-ROM 2
$ MOUNT ddcu:FREEWARE50_2 $ TYPE DISK$FREEWARE50_2:$FREEWARE_README.TXT
In the previous commands, the u in ddcu is the unit number of the CD-ROM device on your system. If you do not know the name of the CD-ROM drive on your system, use the following command:
$ PIPE SHOW DEV DK/FULL | SEARCH SYS$INPUT RRD
Once the appropriate CD-ROM disk is mounted, use the following command to invoke the menu:
This chapter contains information that applies to system maintenance and management, performance management, and networking.
This note pertains to ACMS users, possibly Rdb users, and anyone else running a user-written application that calls DECdtm to participate in a distributed transaction with a remote system having these characteristics:
Users may see the following error, which is returned by DECnet:
IPC-E-BCKTRNSFAIL, failure on the back translate address request
This error is displayed upon a logical connection failure when the remote node name cannot be translated by DECnet-Plus. The error can be triggered when the DECnet-Plus node name for the remote system is not defined in the local DECnet-Plus database and is defined only as ALIAS in the TCP/IP name server for the remote node. For example, node XXYZZY may be defined as follows:
188.8.131.52 XXYZZY.ABC.DEF.COM, XXYZZY
To avoid this situation, either define the node name in the local DECnet-Plus database or define the logical SYS$DECDTM_NODE_NAME to be equivalent to one of the following:
For other requirements and restrictions, refer to the section about
managing DECdtm Services in the OpenVMS System Manager's Manual.
5.1 ECP Data Collector and ECP Performance Analyzer V5.4 Available with V7.3
Starting with the shipment of OpenVMS Version 7.3, the Enterprise Capacity and Performance (ECP) Data Collector Version 5.4 for OpenVMS and the Enterprise Capacity and Performance (ECP) Analyzer Version 5.4 for OpenVMS will be provided to users with a valid operating system license at no additional cost. Both the Data Collector and the Performance Analyzer are also backward compatible with V6.2 (or later) of the OpenVMS operating system at no additional charge. It supports both OpenVMS Alpha and OpenVMS VAX platforms.
The Enterprise Capacity and Performance Data Collector provides data collecting capabilities for input to the Version 5.4 Enterprise Capacity and Performance (ECP) Analyzer for OpenVMS. The Data Collector metrics include CPU, disk I/O, memory, process, network, lock, cluster, and diskset configuration information. The ECP Analyzer provides both graphic (MOTIF-based) and tabular reports for the data assembled by the collector(s), including metrics for CPU, disk I/O, memory, paging, processes, locks, SCS, and TCP/IP.
The Data Collector and the Performance Analyzer are available as down-line loadable kits from the Compaq OpenVMS System Management web page at:
For more information about the new features of the ECP Data Collector and the ECP Performance Analyzer, see the OpenVMS Version 7.3 New Features and Documentation Overview.
Software Support Service for these products is sold separately and is
available on an incremental basis. Please contact your Compaq Services
representative for further details.
5.2 Extended File Specifications
The ODS-5 volume structure supports long file names, allows the use of a wider range of characters within file names and preserves case within file names.
However, the C RTL shipped with OpenVMS Alpha Version 7.3 does not provide full support for extended file names on ODS-5 devices. This lack of full support imposes certain restrictions on users running Netscape FastTrack Server or Apache Web Server for OpenVMS Alpha, or deploying Java applications on an ODS-5 device.
In general, users running Netscape FastTrack Server or Apache Server, or deploying Java applications on OpenVMS can input either UNIX style file names or OpenVMS style file names. (FastTrack and Apache Server usually output UNIX style file names.) With these products, file names are often constructed by the FastTrack server, the Apache server, or the Java Virtual Machine.
Because mixed UNIX and OpenVMS style extended file names are not yet supported by the Compaq C RTL, you may be required to use UNIX style syntax when interacting with Java applications or FastTrack or Apache Server. For example, you may want to modify a root to which you append additional directories or a file name.
The following example illustrates sample mixed UNIX and OpenVMS style file names that are not supported on OpenVMS Alpha Version 7.3:
doc/foo.bar.bar ./tmp/foo.bar.b^_ar ~foo^.bar
However, you can modify the last example so that it will work as an OpenVMS extended file name that has a tilde (~) as the first character. Precede the leading tilde (~) with the extended file specifications escape character (^). For example:
See the OpenVMS Guide to Extended File Specifications for more information about using the tilde (~) in OpenVMS extended file names.
In addition, C RTL functions that return file names do not work correctly if any of the following conditions are true:
If any of the above conditions is true, the following C RTL routines will fail:
Files meeting any of the above conditions will be skipped by the following C RTL routines: