Order Number: AA--RMWWA--TE

This document contains the release notes for Compaq Distributed Computing Environment (DCE) for OpenVMS VAX and OpenVMS Alpha.

Revision/Update Information: This is a new manual.

Operating System: OpenVMS VAX Version 6.2 or higher
OpenVMS Alpha Version 6.2 or higher

Software Version: Compaq DCE for OpenVMS Version 3.0

Compaq Computer Corporation
Houston, Texas

© 2000 Compaq Computer Corporation

Compaq, VAX, VMS, the Compaq logo, and the DIGITAL logo Registered in U.S. Patent and Trademark office.

OpenVMS is a trademark of Compaq Information Technologies Group, L.P.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation.

OSF/1 and UNIX are trademarks of The Open Group.

All other product names mentioned herein may be the trademarks or registered 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 publication is subject to change without notice and is provided "AS IS" WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS INFORMATION REMAINS WITH RECIPIENT. IN NO EVENT SHALL COMPAQ BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, OR LOSS OF BUSINESS INFORMATION), EVEN IF COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING SHALL APPLY REGARDLESS OF THE NEGLIGENCE OR OTHER FAULT OF EITHER PARTY AND REGARDLESS OF WHETHER SUCH LIABILITY SOUNDS IN CONTRACT, NEGLIGENCE, TORT, OR ANY OTHER THEORY OF LEGAL LIABILITY, AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.

The limited warranties for Compaq products are exclusively set forth in the documentation accompanying such products. Nothing herein should be construed as constituting a further or additional warranty.

The OpenVMS documentation set is available on CD-ROM.

This document was prepared using VAX DOCUMENT, Version V3.3-1b.

Contents

RELEASE NOTES

Compaq DCE for OpenVMS VAX and OpenVMS Alpha Version 3.0

Compaq DCE for OpenVMS VAX and OpenVMS Alpha Version 3.0 replaces Digital DCE for OpenVMS VAX and OpenVMS Alpha Version 1.5. Version 3.0 is a complete kit that does not require a previous version of Compaq DCE for OpenVMS for installation. Version 3.0 can be installed on a new system or can be installed as an update to a previous version of DCE for OpenVMS.

Compaq DCE for OpenVMS VAX and OpenVMS Alpha Version 3.0 consists of the following services:

• Remote Procedure Call (RPC) service provides connections between individual procedures in an application across heterogeneous systems in a transparent way.
• Interface Definition Language (IDL) compiler (required for developing distributed DCE applications).
• Threads service provides user-mode control and synchronization of multiple operations. Threads is packaged with the base operating system.
• Cell Directory Services (CDS) provides a location-independent method of identifying resources within a cell. A cell is the smallest group of DCE systems that share a common naming and security domain.
• Distributed Time Service (DTS) provides date and time synchronization within a cell.
• DCE Security Services provides authentication and authorization within a cell and is based upon MIT's Kerberos private key encryption system.

Compaq DCE for OpenVMS VAX and OpenVMS Alpha Version 3.0 includes the following new features. (For more information on these new features, see the Compaq DCE for OpenVMS VAX and OpenVMS Alpha Product Guide, unless otherwise stated.)

• OSF DCE R1.2.2 support --- Compaq DCE for OpenVMS VAX and OpenVMS Alpha Version 3.0 is based on The Open Group's R1.2.2 version of DCE. Full documentation for features common to OSF DCE R1.2.2 is available in the R1.2.2 documentation.
  This version adds the following new features to DCE:
  • dced daemon and dcecp control program
    The RPC daemon (DCE$RPCD.EXE) has been replaced by a combined RPC and security client daemon (DCE$DCED.EXE). In addition, various command line programs (rpccp, cdscp, dtscp, acl_edit, rgy_edit) have been consolidated into a single new program (dcecp).
    The new commands that are available using dcecp can be seen by issuing the following command:

    $ dcecp -c help

  • Auditing
    A new auditing daemon (DCE$AUDITD.EXE) is available in DCE for OpenVMS Version 3.0. The Modify Configuration Menu of the DCE setup command procedure allows this feature to be enabled or disabled, as well as the dcecp command line program.
  • Serviceability enhancements
    See Section 17 for information on using the routing file that is available as part of the new serviceability enhancements.
  • New dtscp commands

    $ dtscp show clock resolution $ dtscp show time provider timeouts detected $ dtscp show local server not in group $ dtscp show servers not in group

  • New dts time providers
    DCE$SETUP.COM now allows you to configure one of the following time providers:

    Null Time Provider
    NTP Time Provider

    
    This functionality can be accessed via the Modify Configuration Menu.
• Kernel Threads and Thread Manager upcalls support --- New in DCE for OpenVMS Version 3.0 is support for running DCE applications with Kernel Threads and upcalls enabled.
• RPC_UNSUPPORTED_NETIFS and RPC_SUPPORTED_NETADDRS --- DCE for OpenVMS Version 3.0 adds the ability to control the use of DCE on systems with multiple network interfaces and/or IP addresses.
• LDAP support --- DCE support for LDAP over GDA (Intercell communication) and LDAP over NSID (Windows NT access to the Name Service Interface) is available in DCE for OpenVMS Version 3.0.
• DCE Privacy Kit included in base DCE kit --- The DCE Privacy kit has been retired, and the functionality has been combined into the base DCE kit. You can now use packet level privacy without a separate kit or license. This funtionality is activated by setting the product_level parameter in the rpc_binding_set_auth_info call to rpc_c_protect_level_pkt_privacy .

Compaq DCE for OpenVMS has four kits available:

• Runtime Services Kit
• Application Developer's Kit
• CDS Server Kit
• Security Server Kit

Note that the right to use the Runtime Services Kit is included as part of the OpenVMS license. The other kits each require a separate license.

The following sections list the contents of each of these kits.

2.1 Runtime Services Kit

The Runtime Services provide the basic services required for DCE applications to function. The Runtime Services Kit contains the following:

• NTLM (Windows NT LAN Manager) security (OpenVMS Alpha Version 7.2-1 and higher only)
• Authenticated CDS Advertiser and Client Support
• CDS Browser
• DCE Control Program (dcecp)
• CDS Control Program (cdscp)
• Authenticated DCE RPC runtime support (supports DECnet, TCP, and UDP)
• RTI (Remote Task Invocation) RPC for the Compaq ACMSxp TP product
• Security Client Support
• Integrated Login
• A DCE_LOGIN tool for obtaining credentials
• A RGY_EDIT tool for registry maintenance functions
• KINIT, KLIST, and KDESTROY Kerberos tools
• An ACL_EDIT tool for access control lists (ACLs) for DCE objects
• RPC Control Program (rpccp)
• Name Services Interface Daemon (nsid); also known as the PC Nameserver Proxy
• Native Kerberos support
• XDS Directory Services
• XDS Object Managment

The Application Developer's Kit is used by developers to build DCE applications. The Application Developer's Kit contains the following:

• The above contents of the Runtime Services Kit
• A mechanism to act as a porting aid in mapping MSRPC calls to DCE RPC calls (OpenVMS Alpha Version 7.2 and higher only)
• Required DCE application development header files
• Interface Definition Language (IDL) compiler
• DCE IDL Compiler with C++ Extensions (Object-Oriented RPC)
• Generic Security Service (GSSAPI)
• LSE Templates for IDL
• UUID Generator
• .H (Include) files and .IDL files for application development
• Sample DCE applications

The CDS Server provides the naming services necessary for DCE clients to locate DCE server applications. The CDS Server Kit includes the following:

• CDS server (cdsd)
• Global Directory Agent (GDA)

The Global Directory Agent (GDA) lets you link multiple CDS namespaces using the Internet Domain Name System (DNS), X.500, or LDAP.

2.4 Security Server Kit

The Security Server provides security services necessary for authenticated RPC calls between DCE client and server applications to function. The Security Server Kit includes the following:

• Security server (secd)
• Tool used to create the security database (sec_create_db)
• Security server administrative tool ( sec_admin )

In addition to shutting down DCE, DCE RPC must also be shut down before installing DCE for OpenVMS Version 3.0. Failure to do so can result in the inability to start DCE for OpenVMS Version 3.0. For DCE for OpenVMS Version 1.5, the following is the proper shutdown order:

1. Shut down DCE and clean up temporary files

   $ @SYS$MANAGER:DCE$SETUP CLEAN

2. Shut down RPC

   $ @SYS$MANAGER:DCE$RPC_SHUTDOWN

If you are running a DCE for OpenVMS version prior to Version 1.5, then executing the first command shuts down both DCE and RPC.

As of OpenVMS Version 7.2, DCE RPC is supplied as part of the OpenVMS operating system, and may be running without a full DCE kit installed. In this situation, you only need to perform the second command listed above to shut down RPC.

Compaq DCE for OpenVMS VAX and OpenVMS Alpha must be installed by running the DCE$INSTALL.COM procedure. Do not install the product by invoking the POLYCENTER Software Installation (PCSI) utility directly. DCE$INSTALL.COM calls PCSI and performs several preinstallation and postinstallation tasks. To install DCE, run the DCE$INSTALL.COM procedure as follows:

$ @ddcu:DCE$INSTALL.COM [help] ! optional PCSI help

See the Compaq DCE for OpenVMS VAX and OpenVMS Alpha Installation and Configuration Guide for more information.

Make sure that you run DCE$INSTALL.COM from a valid directory. Errors may occur during the installation that leave the default directory invalid.

See the first chapter in the Compaq DCE for OpenVMS VAX and OpenVMS Alpha Installation and Configuration Guide for information on installation and configuration prerequisites.

If you are installing DCE for the first time, you must configure DCE before starting it. To configure DCE, enter the following command:

$ @SYS$MANAGER:DCE$SETUP CONFIGURE

3.1 Reconfiguring After Installation

If you are installing a new version of Compaq DCE for OpenVMS VAX and OpenVMS Alpha over an existing version, you do not have to reconfigure DCE after the installation. Before the installation, stop the DCE daemons by entering the following command(s):

$ @SYS$MANAGER:DCE$SETUP CLEAN

If you have DCE for OpenVMS Version 1.5 installed, you must also shut down RPC by issuing the following command:

$ @SYS$MANAGER:DCE$RCP_SHUTDOWN

After the installation, enter the following command:

$ @SYS$MANAGER:DCE$SETUP START

3.2 Configuration Prerequisite on OpenVMS Version 6.2

After installing DCE for OpenVMS Version 3.0 on an OpenVMS Version 6.2 system, you must perform the following operations to enable DCE to operate correctly.

After the first installation of DCE for OpenVMS Version 3.0 on OpenVMS Version 6.2, execute the following command file:

$ @SYS$MANAGER:UTC$TIME_SETUP

Once this command procedure has run, and after DCE has been configured, add the following two lines to the system startup procedure, SYS$MANAGER:SYSTARTUP_VMS.COM:

$ @SYS$MANAGER:DCE$TIME_SETUP $ @SYS$STARTUP:DCE$STARTUP

These command procedures must be called in the order shown above.

4 Troubleshooting

A chapter on troubleshooting is part of the Compaq DCE for OpenVMS VAX and OpenVMS Alpha Product Guide. This chapter includes the following sections:

• General troubleshooting hints
• Time zone and time synchronization problems
• Client/Server Check List

To define foreign commands, have the system manager add the following to your SYLOGIN.COM after the installation:

$ If F$SEARCH("SYS$MANAGER:DCE$DEFINE_REQUIRED_COMMANDS.COM")- .NES. "" THEN @SYS$MANAGER:DCE$DEFINE_REQUIRED_COMMANDS.COM $ If F$SEARCH("SYS$COMMON:[DCE$LIBRARY]DCE$DEFINE_OPTIONAL_COMMANDS.COM")- .NES. "" THEN @SYS$COMMON:[DCE$LIBRARY]DCE$DEFINE_OPTIONAL_COMMANDS.COM

6 Sizing for a Large Number of Users

The DCE daemons require a number of system resources for each concurrent DCE client or server process. The default number of resources allocated to the daemons is based on a maximum of 70 concurrent users (servers and clients) running on a node. If you are running more than 70 DCE users on a node, you must do the following:

1. Stop DCE if it is running.
2. Define a systemwide logical called DCE$MAX_USERS to the maximum number of users desired. For example, to configure DCE for a maximum of 80 users, enter the following:

   $ define/system dce$max_users 80

   
   Add this command to your system startup command file so that it is executed prior to starting DCE.

3. Restart DCE.
   Refer to Section 8 for information about adding TCP/IP sockets if the current number of sockets is insufficient for the number of DCE users running on the node.

The Application Developer's Kit provides support for building DCE applications using DCE Services. It provides Application Programming Interfaces (APIs) to RPC communication services, security services, and CDS name services via the RPC Name Services Interface (NSI). (Version 1.1 of Digital DCE for OpenVMS VAX and OpenVMS Alpha replaced the Local Directory Services (LDS) with the Cell Directory Services (CDS).) The Application Developer's Kit contains the IDL compiler and Runtime support. The header files and IDL files for developing applications are installed in the following directory:

SYS$COMMON:[DCE$LIBRARY]

DCE applications must also be linked with the following shareable image:

SYS$LIBRARY:DCE$LIB_SHR.EXE

This image provides the entry points and global symbol definitions for the DCE API services.

A link options file, SYS$COMMON:[DCE$LIBRARY]DCE.OPT, is also provided. It is recommended that this options file be included when linking your DCE applications. For example:

$ LINK PROG,DCE:DCE/OPT

Linking applications in this way makes your build procedures more portable between OpenVMS VAX and OpenVMS Alpha. It also prevents link environment changes from requiring changes to command files.

To help you port a Microsoft RPC application to the DCE format, a shareable image called SYS$LIBRARY:MSRPC_MAPPING_ SHR.EXE can be used to link with the RPC application. This new image provides entry points that map a subset of Microsoft RPC calls to their DCE equivalents. To identify which APIs have been mapped, see the MSRPC_MAPPING.H file. This file must be included in the RPC application.

8 Using TCP/IP Services for OpenVMS (UCX) with DCE

Compaq DCE for OpenVMS VAX and OpenVMS Alpha Version 3.0 requires modification of several TCP/IP parameters for proper operation. You should carefully look through the parameters discussed in the next sections to understand any impact they may have on your local system.

The changes required depend on which version of Compaq TCP/IP Services for OpenVMS you are using. Most of the modifications listed in this section are not required when using Compaq TCP/IP Services for OpenVMS Version 5.0 or higher. Any changes needed for Version 5.0 or higher are identified in the text.

All parameter changes described below, except for the cdsLib service definition, involve volatile parameters. That is, if TCP/IP is restarted on your system, the parameter settings revert back to UCX-defined defaults, unless the configuration is also modified. The appropriate commands to modify both the volatile and configuration values are shown in the following sections.