Order Number: AA--RMWWB--TE

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

Revision/Update Information: This is a new manual.

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

Software Version: HP DCE for OpenVMS Version 3.1

Hewlett-Packard Company
Palo Alto, California

© 2004 Hewlett-Packard Development Company, L.P.

Microsoft, MSDOS, Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S. and/or other countries.

Intel, Intel Inside, Itanium, and Pentium are trademarks of Intel Corporation in the U.S. and/or other countries.

UNIX is a trademark of The Open Group in the U.S. and/or other countries.

Confidential computer software. Valid license from HP and/or its subsidiaries 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 vendors standard commercial license.

Neither HP nor any of its subsidiaries shall 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 HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an 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

HP DCE for OpenVMS VAX and OpenVMS Alpha Version 3.1

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

Version 3.1 of HP DCE for OpenVMS VAX and OpenVMS Alpha 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.

HP DCE for OpenVMS VAX and OpenVMS Alpha Version 3.1 is an enhanced version of its previous Version 3.0. All the new features of Compaq DCE for OpenVMS Version 3.0 described in Section 1.2 are also applicable to DCE for OpenVMS Version 3.1.

Version 3.1 of HP DCE for OpenVMS VAX and OpenVMS Alpha includes the following new features.

• Support for Time Synchronization with DECnet Time Service
  • The DCE Time Service daemon and command line program DTSCP have been enhanced to support the time synchronization with DECnet time service.
  • The following are the DTSCP commands for DCE DTSS to synchronize with DECnet DTSS:

    $ dtscp set decnet time source true $ dtscp set decnet time source false $ dtscp show decnet time source $ dtscp show decnet local server $ dtscp show all In addition to the existing attributes in DCE for OpenVMS Version 3.0, the DECnet related attributes DECnet Courier Role, DECnet Acting Courier Role, DECnet Time Source would be displayed in DCE Version 3.1. $ dtscp help show In addition to the existing attributes on DCE for OpenVMS Version 3.0, the DECnet related attributes DECnet Courier Role, DECnet Acting Courier Role, DECnet Time Source will be displayed in DCE Version 3.1. $ dtscp help set In addition to the existing attributes on DCE for OpenVMS Version 3.0, the DECnet related attribute DECnet Time Source will be displayed in DCE Version 3.1.

• CDS Migration
  • DCECP command line control program enhanced to support the CDS directory migration from 3.0 to 4.0.
  • The following command can be used to upgrade older directory version information to 4.0:

    dcecp> directory modify <dir name> -upgrade -tree (or) $ dcecp -c directory modify <dir name> -upgrade -tree

• TRY_PE_SITE Option
  The DCE$LOCAL:[ETC.SECURITY]PE_SITE.file can be used for security server load balancing. If the CDS server is down, the file can be used to locate the security replica. The logical TRY_PE_SITE regulates the search order for locating the DCE security server.
  • If TRY_PE_SITE is set to 1, the client will attempt to locate the security replica using the pe_site file. If it fails, the client will locate the security replica through CDS namespace. If both TRY_PE_ SITE and bind_pe_site are set to 1, TRY_PE_SITE behavior takes precedence.
  • If logicals TRY_PE_SITE and BIND_PE_SITE are not set (or) are set to 0, then client will locate the security replica through CDS namespace.
• Performance Improvement in CDS Clerk
  The DCE Version 3.1 includes the TRY_PE_SITE option for the DCE CDS Clerk process alone. To use this, enable the CDSCLERK_TRY_PE_SITE logical. This can result in better performance for CDS operation.

  $ DEFINE/SYSTEM CDSCLERK_TRY_PE_SITE TRUE

  
  

• Fixes in DCE Version 3.1
  The details of the fixes included in HP DCE for OpenVMS Alpha and OpenVMS VAX Version 3.1 are described in the Section 20 of this document.

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 and Compaq DCE for OpenVMS Version 3.0 is available in the R1.2.2 documentation. (For more information on these new features, see the Compaq DCE for OpenVMS VAX and OpenVMS Alpha Product Guide, unless otherwise stated.)

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 19 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 protect_level parameter in the rpc_binding_set_auth_info call to rpc_c_protect_level_pkt_privacy .

HP 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 HP 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)
• CDS Checkpoint Migrate Tool (CHKMIGRATE)

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

The Checkpoint migration tool should be used to migrate the checkpoint file present in the DCE$LOCAL:[VAR.DIRECTORY.CDS] directory when upgrading the DCE for OpenVMS Version 1.5 to Version 3.1 of DCE and before starting DCE for OpenVMS Version 3.1.

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 )

The Product Guide, Reference Guide, Installation and Configuration Guides of Compaq DCE for OpenVMS Version 3.0 are applicable for HP DCE for OpenVMS Version 3.1 as well.

4 Installation/Configuration Prerequisites

• The DCE MUST be shut down before installing DCE for OpenVMS Version 3.1. Failure to do so can result in inability to start DCE for OpenVMS Version 3.1.
• When you install DCE Version 3.1 on OpenVMS Version 7.3 and above, in order to receive all the Version 3.1 RPC runtime updates you MUST install the corresponding RPC patch kit for OpenVMS.
  Minimum version of RPC patch kits for OpenVMS Alpha and VAX versions are listed below:

  VMS73_RPC-V0200 : RPC Kit for OpenVMS Alpha V7.3 VMS731_RPC-V0200 : RPC Kit for OpenVMS Alpha V7.3-1 VMS732_RPC-V0100 : RPC Kit for OpenVMS Alpha V7.3-2 VMS73_RPC-V0100 : RPC Kit for OpenVMS VAX V7.3

For example, if you are installing DCE for OpenVMS Version 3.1 product on OpenVMS Version 7.3-1 for Alpha, you would need to install ‘‘VMS731_ RPC_V0200’’.

4.1 DCE Upgrade and Configuration

If you are installing a new version of HP DCE for OpenVMS VAX and OpenVMS Alpha over an existing version, you do not have to reconfigure DCE after the installation.

For DCE for OpenVMS Version 1.5, the proper shutdown order should be as follows:

1. Shut down DCE and clean up temp files

   $ @SYS$MANAGER:DCE$SETUP CLEAN

2. Shut down RPC

   $ @SYS$MANAGER:DCE$RPC_SHUTDOWN

If you are running a DCE Version 3.0 for OpenVMS, then simply performing the first command will shut 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 (RPC Only configuration) without a full DCE kit installed. In this situation, you only need to perform the second command listed above to shut down RPC.

Install the corresponding RPC patch kit on your system, if you are running OpenVMS Version 7.3 and above.

HP DCE for OpenVMS VAX and OpenVMS Alpha Version 3.1 must be installed by running the DCE$INSTALL.COM procedure. Do not install the product by invoking the POLYCENTER Software Installation utility (PCSI) 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 DCE for OpenVMS VAX and OpenVMS Alpha Installation and Configuration Guide for more information.

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

After the installation, enter the following command to start HP DCE for OpenVMS Version 3.1.

$ @SYS$MANAGER:DCE$SETUP START

If you are installing DCE for OpenVMS Version 3.1 for the first time, you need to follow the below procedure.

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

$ @SYS$MANAGER:DCE$RPC_SHUTDOWN CLEAN

Install the corresponding RPC patch kit on your system, if you are running OpenVMS Version 7.3 and above.

HP DCE for OpenVMS VAX and OpenVMS Alpha Version 3.1 must be installed by running the DCE$INSTALL.COM procedure. Do not install the product by invoking the POLYCENTER Software Installation utility (PCSI) 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 DCE for OpenVMS VAX and OpenVMS Alpha Installation and Configuration Guide for more information.

You must configure DCE before starting it. Enter the following command for DCE configuration:

$ @SYS$MANAGER:DCE$SETUP CONFIGURE

5 Troubleshooting

A chapter on troubleshooting is part of the 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

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

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). 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.