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

Revision/Update Information: This is a new manual.

Operating System: OpenVMS Alpha Version 7.3-2 and higher
OpenVMS I64 Version 8.2

Software Version: HP DCE for OpenVMS Version 3.2

Hewlett-Packard Company
Palo Alto, California

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

Confidential computer software. Valid license from HP 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.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

All Java and Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries.

Oracle is a US registered trademark of Oracle Corporation, Redwood City, California.

OSF and Motif are trademarks of The Open Group in the US and other countries.

UNIX is a registered trademark of The Open Group.

Microsoft, Windows, Windows NT, and MS Windows are US registered trademarks of Microsoft Corporation.

X/Open is a registered trademark, and the X device is a trademark of X/Open Company Ltd. in the UK and other countries.

Printed in the US

The HP OpenVMS documentation set is available on CD-ROM.

This document was prepared using VAX DOCUMENT, Version 2.1.

Contents

RELEASE NOTES

HP DCE for OpenVMS Alpha and OpenVMS I64 Version 3.2

HP DCE for OpenVMS Alpha Version 3.2 replaces HP DCE for OpenVMS Alpha Version 3.1. HP DCE for OpenVMS Industry Standard 64 (I64) Version 3.2 is the first release on OpenVMS I64 platform. Version 3.2 is a complete kit that does not require a previous version of HP DCE for OpenVMS for installation. Version 3.2 can be installed on a new system or can be installed as an update to a previous version of DCE.

Version 3.2 of HP DCE for OpenVMS 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.

Version 3.2 of HP DCE for OpenVMS includes the following new features:

• I64 Support
  Version 3.2 is the first ported version of HP DCE on OpenVMS I64.
• HP DCE V3.2 for OpenVMS Alpha is an enhanced version of its previous Version 3.1. All the new features of HP DCE V3.1 for OpenVMS Alpha and OpenVMS VAX as described in section 1.2 are also applicable to HP DCE Version 3.2 for OpenVMS Alpha and I64.
• DCE RPC Now Supports IEEE Floating Point Type
  DCE RPC for OpenVMS now supports both G_FLOAT and IEEE floating point types on Alpha and I64 platforms. The default floating-point type on Alpha platform remains G_FLOAT. The default floating-point type on I64 is IEEE_FLOAT. DCE RPC Application developers would need to use rpc_set_local_float_drep call in their application for using the non-default floating point type. DCE RPC on VAX platform only supports G_FLOAT type. Please refer section [15] for more details.
• Support for tuning the buffer size of RPC Sockets
  The RPC runtime created sockets do not depend on the system specified socket buffer size values while setting the buffer quotas. They depend on the internally defined macros that set the buffer size to a default value of 4K bytes. RPC Runtime now provides support for tuning the socket buffer size by means of a logical "RPC_USE_DEFAULT_SOCKET_BUFFER_ SIZE". Setting the logical "RPC_USE_DEFAULT_SOCKET_BUFFER_ SIZE" will allow RPC Runtime to make use of the system default socket buffer size values. The logical can be defined system wide as follows:

  $DEFINE /SYSTEM RPC_USE_DEFAULT_SOCKET_BUFFER_SIZE 1

  
  To restore the original RPC Runtime behavior the logical will need to be deassigned.

• DCE RPC Supports FAILSafe IP
  DCE RPC has been enhanced to work in a FAILSafe IP environment.
• Fixes in DCE V3.2
  The details of the fixes included in HP DCE V3.2 for OpenVMS are described in Section 19 of this document.

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 are also applicable to DCE for OpenVMS Version 3.1. Please refer the release notes of Compaq DCE for OpenVMS Alpha and OpenVMS VAX Version 3.0 for more details on the new features.

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 HP 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 HP 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 HP 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 facilitates Security Server load balancing and locating of Security Server when the CDS server is down. DCE has been enhanced to first use pe_site file and then the CDS namespace for locating the security server. Defining TRY_PE_SITE logical enables this functionality.
  • 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 use the traditional method of locating the 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
  CDS clerk has been enhanced to use the TRY_PE_SITE option. To use this enhancement 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.

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)

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 )

If DCE is being installed on a prior version (DCE Version 3.0 or DCE Version 3.1), you will need to shutdown or clean DCE. Failure to do so can result in inability to start DCE. HP DCE V3.2 is the first release for OpenVMS I64 systems and needs to be installed afresh.

• When you install DCE Version 3.2 on OpenVMS Version 7.3-2 in order to receive all the Version 3.2 RPC runtime updates you MUST also install the RPC Runtime V4.0 Kit that applies to V3.2.

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

If you are running DCE Version 3.0 or Version 3.1 for OpenVMS, you MUST shutdown or clean DCE making use of the following procedure.

$ @SYS$MANAGER:DCE$SETUP STOP or $ @SYS$MANAGER:DCE$SETUP CLEAN

A DCE clean will also cleanup the temporary database files and is always recommended. Shutting down DCE will also shutdown 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 will need to shut down or clean RPC as follows.

$ @SYS$MANAGER:DCE$RPC_SHUTDOWN or $ @SYS$MANAGER:DCE$RPC_SHUTDOWN CLEAN

HP DCE V3.2 for OpenVMS Alpha and OpenVMS I64 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 pre-installation and post-installation tasks. To install DCE, run the DCE$INSTALL.COM procedure as follows:

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

See the HP DCE for OpenVMS Alpha and OpenVMS I64 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 V3.2.

$ @SYS$MANAGER:DCE$SETUP START

3.2 DCE Installation and Configuration

If you are installing HP DCE for OpenVMS Version 3.2 for the first time, follow the below procedure.

As of OpenVMS Version 7.2, DCE RPC is supplied as part of the HP 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 RPC patch V4.0 Kit on your system using PRODUCT INSTALL if your running HP OpenVMS Alpha Version 7.3-2.

To install DCE, run the DCE$INSTALL.COM procedure as follows:

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

See the HP DCE for OpenVMS Alpha and OpenVMS I64 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

4 Troubleshooting

A chapter on troubleshooting is part of the HP DCE for OpenVMS Alpha and OpenVMS I64 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 system-wide 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.