HP OpenVMS Systems Documentation

V7.3

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.

3.10 MultiNet® Version 4.3

V7.3

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:

V7.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:

• Create a backup copy of the SYS$LOADABLE_IMAGES:SYS$GYCDRIVER.EXE image. Once Open3D is installed, restore the backup copy of SYS$LOADABLE_IMAGES:SYS$GYCDRIVER.EXE.
• Do not purge files during the Open3D installation, and enter the following command after installation:

  $ RENAME SYS$LOADABLE_IMAGES:SYS$GYCDRIVER.EXE;-1 ;0

V7.3

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.

3.13 DEC PL/I---RTL Support for OpenVMS

V7.3

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:

Image Identification Information

        image name: "DPLI$RTLSHR"
        image file identification: "V4.0-6"

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:

Kednos Corporation
2857 Sloat Rd.
Pebble Beach, CA. 93953
Phone: (831) 373-7003

V7.3

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, 51.04.xx.

3.15 Compaq TCP/IP Services for OpenVMS

This section contains release notes pertaining to Compaq TCP/IP Services for OpenVMS and DIGITAL TCP/IP Services for OpenVMS.

3.15.1 Compaq TCP/IP Services for OpenVMS Version 5.1 New Features

V7.3

New features in TCP/IP Services Version 5.1 include:

• New kernel, based on Compaq Tru64 UNIX V5.1
• Support for Internet Protocol Version 6 (IPv6)
• GATED enhancements
• Services that can be restarted individually
• Cluster failover for the Berkeley Internet Name Domain (BIND) server
• BIND dynamic updates management enhancements
• Updated Simple Network Management Protocol (SNMP) that supports AgentX
• SMTP AntiSPAM (configuration to control mail relay)
• SMTP SFF (Send From File)
• SMTP outbound alias
• Metric server logicals that can be changed without restarting the Metric server
• Cluster failover for LBROKER
• DHCP server can be configured to dynamically update BIND database
• Xterminal support using XDM
• TELNET client enhancements to support SNDLOC and NAWS
• NFS server and client enhancements
• DHCP client support

For information about upgrading to TCP/IP Services for OpenVMS Version 5.1, see the Compaq TCP/IP Services for OpenVMS Release Notes.

3.15.2 DIGITAL TCP/IP Services for OpenVMS Version 4.2 (UCX) Not Supported

V7.3

DIGITAL TCP/IP Services for OpenVMS Version 4.2 (UCX) is not supported on OpenVMS Version 7.0 and later releases.

This chapter provides information for all users of the OpenVMS operating system. It includes information about commonly used commands and utilities.

For information about new features included in this version of the software, refer to the OpenVMS Version 7.3 New Features and Documentation Overview.

4.1 AlphaServer GS Series Systems

This section contains release notes of general interest to most users of the AlphaServer GS Series Systems.

4.1.1 AlphaServer GS Series Systems Supported in OpenVMS Version 7.3

V7.3

OpenVMS Version 7.3 includes support for Compaq AlphaServer GS80, GS160, and GS320 systems. This support includes:

• OpenVMS support for hard and soft (Galaxy) partitions on AlphaServer GS80, GS160, and GS320 systems
• OpenVMS Resource Affinity Domain (RAD) support for applications
• OpenVMS support for CPU online replace

For complete information about using hard partitions, OpenVMS Galaxy, or the OpenVMS RAD features to manage OpenVMS workloads on the new Alpha Server GS Series systems, refer to the OpenVMS Alpha Partitioning and Galaxy Guide.

4.1.2 OpenVMS Galaxy License Enforcement

V7.3

In an OpenVMS Galaxy computing environment, the OPENVMS-GALAXY license units are checked during system startup and whenever a CPU reassignment between instances occurs.

If you attempt to start a CPU and there are insufficient OPENVMS-GALAXY license units to support it, the CPU will remain in the instance's configured set but it will be stopped. You can subsequently load the appropriate license units and start the stopped CPU while the system is running. This is true of one or more CPUs.

4.1.3 V5.9B Console Firmware Required for OpenVMS on AlphaServer GS80/160/320 Systems

V7.3

If you are running OpenVMS Alpha Version 7.3 on AlphaServer GS80/160/320 systems, you must download console firmware V5.9B or later from the following location:

Note that you need the V5.9B console firmware to use the new CPU online replace feature.

4.1.4 Device Restriction on AlphaServer GS80/160/320 Systems

V7.3

Only one set of the following devices found on the legacy bus adapter is configured and supported per partition in OpenVMS Alpha Version 7.3. These devices include:

• Serial ports COM1 and COM2
• Parallel port
• Keyboard
• Mouse

If multiple legacy bus adapters exist, only the adapter that includes the console port is configured and supported.

4.1.5 Booting an AlphaServer GS140

V7.3

If you are booting an AlphaServer GS140 system with a Fibre Channel HSG80 system disk using Alpha Firmware Version 5.7, the system fails to reboot when the system is set to boot automatically. Enter the following command to show whether the system has been set to boot automatically:

SHOW AUTO_ACTION

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:

SHOW CONFIGURATION

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

V7.3

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

V7.3

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:

ACL_Editor
BACKUP_API
CLI_Routines
CONV$_Routines
CQUAL_Routines
DCX_Routines
DECTPU
EDT_Routines
FDL_Routines
LBR_Routines
LGI_Routines
MAIL_Routines
NCS_Routines
PSM_Routines
SMB_Routines
SOR_Routines

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:

A few more changes and additions have been made to Help topics:

• Help for the MIME utility has been added to both Alpha and VAX systems.
• DECthreads Help has been replaced with the POSIX_Threads Help topic. This change reflects a product name change.
• Help formerly located under DPML on Alpha systems is now found under CPML to reflect the product name change to Compaq Portable Mathematics Library routines.
• On Alpha systems, Help has been added for WWPPS (World-Wide PostScript Printing Subsystem).
• The CDA messages that used to be included under the CONVERT Help topic can now be accessed using the Help Message facility.
• The DVR$ messages that used to be included under the VIEW Help topic can now be accessed using the Help Message facility.

V7.3

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.

Note:

• If you are running OpenVMS Version 7.3 on AlphaServer GS80/160/320 systems, you need console firmware V5.9B, which you can download from the following location:
  http://h18002.www1.hp.com/alphaserver/firmware/
  
• If you are running OpenVMS Version 7.3 on AlphaServer GS80/160/320 systems, you need the V5.9B console firmware to use the new CPU online replace feature.
• If you are running OpenVMS Version 7.3 on AlphaServer GS60E/140 systems, do not use Version 5.9-2 firmware. Access the following web site for firmware V5.9B and the most current information on firmware:
  http://h18002.www1.hp.com/alphaserver/firmware/

V7.3

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:[000000]$FREEWARE_README.TXT

Freeware CD-ROM 2

$ MOUNT ddcu:FREEWARE50_2
$ TYPE DISK$FREEWARE50_2:[000000]$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:

@DISK$FREEWARE:[FREEWARE]FREEWARE_MENU

This chapter contains information that applies to system maintenance and management, performance management, and networking.

For information about new features included in this version of the software, refer to the OpenVMS Version 7.3 New Features and Documentation Overview.

V7.3

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:

• The network connection is Compaq DECnet-Plus for OpenVMS over TCP/IP.
• The nodes are connected using only an IP router.

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:

20.43.136.54    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:

• The value of the SYSGEN parameter SCSNODE
• The DECnet-Plus simple name
• The TCP/IP alias (that is, a six-character node name string such as XXYZZY, as shown in the preceding example)

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

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

V7.3

Mixed UNIX and OpenVMS Style File Names Not Supported

This release note pertains to Extended File Specifications. For more information about Extended File Specifications, see the OpenVMS Guide to 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:

^~foo^.bar

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:

• The VMS file specification contains ODS-5 characters.
• The VMS file specification contains a directory name in Directory ID (DID) format.
• The VMS file specification contains a file name in File ID (FID) format.
• The file specification is larger than the receiving buffer.

If any of the above conditions is true, the following C RTL routines will fail:

getname()
fgetname()
getcwd()
decc$from_vms()
decc$translate_vms()

Files meeting any of the above conditions will be skipped by the following C RTL routines:

ftw()
readdir()

These mixed UNIX and OpenVMS style file names will be supported in a future release of Compaq C RTL for OpenVMS.