Document revision date: 19 July 1999

This section contains important release notes for existing users of Digital Distributed Computing Environment (DCE) for OpenVMS VAX and OpenVMS Alpha.

Beginning with OpenVMS Version 7.2, Remote Procedure Call (RPC) functionality is integrated into the operating system. For more information about RPC functionality, refer to the OpenVMS Version 7.2 New Features Manual.

For more information about Digital DCE for OpenVMS, refer to the following documentation:

• Digital DCE for OpenVMS VAX and OpenVMS Alpha Installation and Configuration Guide (Order number AA-Q70GB-RE)
• Digital DCE for OpenVMS VAX and OpenVMS Alpha Product Guide (Order number AA-Q70FC-RE)
• Digital DCE for OpenVMS VAX and OpenVMS Alpha Reference Guide (Order number AA-Q70JC-RE)

The following section describes changes to DCE.

2.13.1.1 DCE System Management Command Procedure

V7.2

With the integration of the RPC daemon in OpenVMS Version 7.2, the following enhancements have been made to the DCE system management command procedure (DCE$SETUP.COM):

• RPC can be started with the new startup command procedure, DCE$RPC_STARTUP.COM. For information about how to start the RPC daemon, see the OpenVMS Version 7.2 New Features Manual.
• DCE$SETUP no longer directly starts the RPC daemon. It now calls DCE$RPC_STARTUP.
• DCE$SETUP no longer performs UCX parameter checking. This is performed by DCE$RPC_STARTUP.
• DCE$SETUP no longer stops the RPC daemon under any circumstances. The RPC daemon can be stopped only by calling DCE$RPC_SHUTDOWN.
• DCE$RPC_SHUTDOWN checks to see if any DCE components are running before it stops the RPC daemon.
• DCE components can be started, stopped, or configured without shutting down the RPC daemon.
• Invoking DCE$SETUP with the CLEAN or CLOBBER option no longer deletes the RPC endpoint database (DCE$LOCAL:[VAR.RPC]RPCDEP.DAT). However, the endpoints for any DCE components will be removed. The only way to delete the entire RPC endpoint database is to invoke the DCE$RPC_SHUTDOWN procedure with the CLEAN option.
• Small modifications to some informational messages have been made to remind the user of the above changes.

The following section describes a restriction associated with DCE for OpenVMS Version 1.5.

2.13.2.1 Authenticated RPC Functionality Not Available

V7.2

The new authenticated RPC functionality in DCE for OpenVMS Version 1.5, including impersonation and authentication with NT Lan Manager (NTLM) protocol, is not included in OpenVMS Version 7.2.

You can install DCE for OpenVMS Version 1.5 and use the existing functionality, but all new functionality related to using NTLM and impersonation is not available.

Compaq intends to provide support for the new DCE for OpenVMS features after OpenVMS Version 7.2. Customers will be notified how to obtain the software when support is available.

The Digital DCE for OpenVMS VAX and OpenVMS Alpha documentation that ships with OpenVMS Version 7.2 provides information on NTLM as a preview of functionality that will be available in a future version of Digital DCE for OpenVMS Alpha. This advanced documentation will help you plan for the future.

2.14 DIGITAL TCP/IP Services for OpenVMS

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

2.14.1 Changes and Enhancements

The following note describes changes introduced with Version 5.0 of DIGITAL TCP/IP Services for OpenVMS.

2.14.1.1 Changes in Version 5.0

V7.2

Starting with OpenVMS Version 7.2, DIGITAL TCP/IP Services for OpenVMS Version 5.0 replaces Version 4.2 (also known as UCX). Version 5.0 completes the change initiated several releases ago when the product name changed from ULTRIX Connection (UCX) to DIGITAL TCP/IP Services for OpenVMS.

The identifier UCX is replaced with TCPIP in the following items:

• Registered product facility code
• Management command prompt
• All messages, examples, and banners
• All product file names and databases
• All logical names
• All associated product documentation

This release provides backward compatibility for all UCX logical names and support for UCX commands.

At this time, customers do not need to upgrade their applications or command procedures that rely on UCX names. UCX$DEVICE will continue to work as always. However, Compaq encourages customers to use the new naming convention as soon as possible. Support for the old naming is not guaranteed in subsequent releases.

No changes to the LMF (License Management Facility) Product Authorization Keys are required.

Changes in this release include the following:

• Support for external authorization
• File Transfer Protocol (FTP) enhancements, including support for Extended File Specifications
• Enhanced socket-based application programming interface
• Time zone configuration changes
• NFS and SMTP changes
• Obsolescence of some management commands

Additional new features are outlined in the OpenVMS Version 7.2 New Features Manual and details are provided in the release notes that ship with the DIGITAL TCP/IP Services for OpenVMS Version 5.0 kit.

For information about installing DIGITAL TCP/IP Services for OpenVMS, refer to the manual DIGITAL TCP/IP Services for OpenVMS Installation and Configuration.

2.15 PATHWORKS for OpenVMS

This section contains release notes pertaining to PATHWORKS for OpenVMS.

2.15.1 Changes and Enhancements

The following release note summarizes a change in support for PATHWORKS for OpenVMS products.

2.15.1.1 PATHWORKS Advanced Server V6.0/6.0A Replacement

V7.2

PATHWORKS for OpenVMS (Advanced Server) Version 6.0 and Version 6.0A are not supported on OpenVMS Version 7.2.

You can run either PATHWORKS V6.0B for OpenVMS (Advanced Server) or the Advanced Server V7.2 for OpenVMS. Both are supported on OpenVMS Version 7.2 systems.

PATHWORKS V6.0B for OpenVMS (Advanced Server) runs on either OpenVMS Alpha Version 7.2 or OpenVMS VAX Version 7.2 systems. You will want to run PATHWORKS V6.0B if you want to provide file and print services from an OpenVMS VAX Version 7.2 system, either in a cluster or standalone.

Advanced Server V7.2 for OpenVMS (see Section 2.2) runs only on OpenVMS Alpha Version 7.2 systems. You can run Advanced Server V7.2 for OpenVMS in a mixed-architecture cluster, using an external authentication VAX module included in the kit.

2.15.1.2 PATHWORKS V5 for OpenVMS (LAN Manager) Not Supported

V7.2

PATHWORKS V5 for OpenVMS (LAN Manager) is not supported on OpenVMS Version 7.2.

If you are running PATHWORKS V5 for OpenVMS (LAN Manager) and want to offer file and print services after you install OpenVMS Version 7.2, you must upgrade the file and print server to PATHWORKS V6.0B for OpenVMS (Advanced Server) before you install OpenVMS Version 7.2. For information about upgrading from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS V6 for OpenVMS (Advanced Server), refer to the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide provided with the kit documentation.

You cannot upgrade directly from PATHWORKS V5 for OpenVMS (LAN Manager) to the Advanced Server V7.2 for OpenVMS.

2.16 POSIX for OpenVMS

This section contains release notes about POSIX for OpenVMS.

2.16.1 Problems and Restrictions

The following note describes a support restriction for POSIX for OpenVMS.

2.16.1.1 POSIX for OpenVMS Is Not Supported

V7.2

POSIX for OpenVMS is not supported on OpenVMS Version 7.2. The POSIX for OpenVMS product has been retired. For more information, see Section A.6.

This section contains a release note pertaining to the Process MultiNet for OpenVMS product.

2.17.1 Changes and Enhancements

The following note describes a version update requirement.

2.17.1.1 Update Required for OpenVMS Alpha Version 7.2

V7.2

If you want to use Process MultiNet for OpenVMS on OpenVMS Alpha Version 7.2, you must either upgrade to MultiNet Version 4.1B or install the Version 4.1A patch KERNEL-UPDATE-30_A041, which is accessible using anonymous FTP from the following location:

MultiNet and TCPware customers should contact Process Software for ECO kits that should be applied to systems running OpenVMS Alpha Version 7.2. Contact information is as follows:

• Telephone: 1-800-394-8700
• E-mail: support@process.com
• World Wide Web: http://www.process.com

V7.1

Bristol Technology's Wind/U products are used by independent software vendors (ISVs) and developers to create Windows based applications that can be deployed across multiple computing environments.

Bristol Technology's Wind/U Run-Time Library for OpenVMS is distributed with the OpenVMS Version 7.2 kit. However, you must directly contact Bristol Technology for the Wind/U Developer's Kit as well as for licenses and support for both the Run-Time Library and the Developer's Kit.

To obtain your product authorization key (PAK) to access Wind/U for OpenVMS, contact Bristol Technology as follows:

• Bristol Technology Inc.
  241 Ethan Allen Highway, Ridgefield, CT 06877 USA
  (203) 438-6969
  email: info@bristol.com

For more information about Wind/U for OpenVMS, access the Bristol Technology web site.

	privacy and legal statement
6534PRO_006.HTML