HP DCE for OpenVMS Alpha and OpenVMS I64

Installation and Configuration Guide

Order Number: BA361-90001

January 2005

This guide describes the installation procedure and the system configuration utility for the HP Distributed Computing Environment (DCE) for OpenVMS Alpha and OpenVMS I64.

Revision/Update Information: This guide supersedes the Compaq DCE for OpenVMS VAX and OpenVMS Alpha Installation and Configuration Guide Version 3.0.

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

Software Version: HP DCE for OpenVMS Version 3.2

Hewlett-Packard Company
Palo Alto, California

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

ZK6531

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

This document was prepared using DECdocument, Version V3.3-1e.

Contents Index

Preface

This guide describes the installation procedure and the system configuration utility for the HP Distributed Computing Environment (DCE) for OpenVMS Alpha and OpenVMS Industry Standard 64 (I64) Version 3.2, which consists of the following services:

Remote Procedure Call (RPC) service provides connectivity between individual procedures in an application across heterogeneous systems in a transparent way.
Interface Definition Language (IDL) compiler is 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 Service (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.
DCE Security Service provides authentication and authorization within a cell and is based on MIT's Kerberos private key encryption system.
Distributed Time Service (DTS) provides date and time synchronization within a cell.

Four kits are installed:

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

The Runtime Services Kit contains the following:

Authenticated CDS Advertiser and Client Support
CDS Browser
CDS Control Program (cdscp)
Authenticated DCE RPC runtime support (supports DECnet, TCP/IP, and UDP)
Authenticated RPC runtime support (supports DECnet, TCP/IP, and UDP via NTLM security protocol on OpenVMS Alpha Version 7.2-1 and higher.)
RTI (Remote Task Invocation) RPC for HPs ACMSxp TP product on OpenVMS Alpha systems
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)
DCE Control Program (dcecp)
Name Service Interface Daemon (nsid); also known as the PC Nameserver Proxy
Native Kerberos
XDS Directory Services
XDS Object Management

The Application Developer's Kit contains the following:

The contents of the Runtime Services Kit
Required DCE application development header files
Interface Definition Language (IDL) compiler
Object-Oriented RPC
Generic Security Service (GSSAPI)
LSE Templates for IDL
UUID Generator
The .H (Include) files and .IDL files for application development
Sample DCE applications

The CDS Server Kit contains the following:

CDS server (cdsd)
Global Directory Agent (GDA)
PC Name Service Interface Daemon (nsid)

The Security Server Kit contains the following:

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

Keep this document with your distribution kit. You will need it to install maintenance updates or to reinstall HP DCE.

Intended Audience

This guide is intended for managers of distributed computing environments on one or more systems and installers of the HP DCE for OpenVMS Alpha or OpenVMS I64 Version 3.2.

Document Structure

This guide is organized as follows:

Chapter 1 describes the requirements and procedures that you must complete before installing the software.
Chapter 2 describes the installation process.
Chapter 3 describes procedures that you must complete after the installation.
Chapter 4 describes the steps necessary to set up a DCE cell, and the DCE system configuration utility for HP DCE for OpenVMS Alpha and OpenVMS I64.
Chapter 5 explains how to create a cell and configure the Security server and CDS server on the same system. It also discusses how to configure a client system into an existing DCE cell.
Chapter 6 describes the steps you need to complete to modify a cell configuration.
Appendix A lists the directories and files created by the installation procedure and system configuration utility.
Appendix B contains sample logs of the installation procedure.
Appendix C contains sample logs of the configuration procedure.

Reader's Comments

HP welcomes your comments on this manual. Please send comments to either of the following addresses:

Internet openvmsdoc@hp.com

Postal Mail Hewlett-Packard Company
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How To Order Additional Documentation

For information about how to order additional documentation, visit the following World Wide Web address:

http://www.hp.com/go/openvms/doc/order

Conventions

VMScluster systems are now referred to as OpenVMS Cluster systems. Unless otherwise specified, references in this document to OpenVMS Clusters or clusters are synonymous with VMSclusters.

The following conventions are used in this guide:

Ctrl/ x A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.

italic text Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where device-name contains up to five alphanumeric characters).

UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.

Monospace text Monospace text indicates code examples and interactive screen displays.
In the C programming language, monospace text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.

Case-sensitivity OpenVMS operating system commands do not differentiate between uppercase and lowercase. However, many DCE commands do make this distinction. In particular, the system configuration utility interprets names in a case-sensitive manner.

Chapter 1
Preparing for Installation

This chapter describes the preparations you must make before you install and configure the HP Distributed Computing Environment (DCE) for OpenVMS Alpha and OpenVMS I64 software.

HP DCE is an enabling software technology for the development of distributed applications. It provides a variety of common services needed for the development of distributed applications, such as name services and a standard remote procedure call interface.

1.1 Planning for Installation and Configuration

This section helps you plan for the installation and configuration of the HP DCE. It presents a brief overview of some concepts that you need to understand before you install and configure HP DCE software. This understanding can help you decide how to configure DCE. Refer to Understanding DCE for detailed explanations of DCE concepts.

The installation and configuration procedures set up the DCE environment so that you can use DCE services. Before you can use HP DCE software, you must both install the software and configure DCE on your system.

1.1.1 What Is a Cell?

A cell is the basic DCE unit consisting of a group of nodes that share a directory service namespace and a security service registry under a common administration. Usually, the nodes in a cell are in the same geographic area, but cell boundaries are not limited by geography. Although a cell can contain from one to several thousand nodes, each node can belong only to one cell at a time.

The system configuration utility allows you to join an existing cell. The cell must provide a directory server and a security server. These servers may be resident on the same system or may be running on separate systems.

Note that if you rely on DCE time services for time synchronization, by default, you need a minimum of three time servers to synchronize time in a cell. See the section on the DCE Distributed Time Service in the OSF DCE Administration Guide for more information.

1.1.2 Creating a Cell

See Chapter 4 for cell configuration guidelines.

1.1.3 Joining a Cell

You need the following information to join a DCE cell:

Full cell name
Host name of the DCE Security Server
Security principal name and password authorized to perform cell administration operations
Location of the cell's CDS server (on or not on the same LAN as you are)

When the client joining the cell is on the same LAN as the CDS directory master server, the CDS advertiser automatically determines the server's location by using IP (Internet Protocol) broadcast packets. If the CDS master server is not on the LAN, then you need to provide the host name where the CDS master server is running.

1.2 Inspecting the Distribution Kit

The Software Bill of Materials (BOM) included with your distribution kit specifies the contents of your distribution kit. Carefully compare the items you received with the items listed in the BOM. If any components are missing or damaged, contact your HP customer service representative before you continue with the installation.

The Read Before Installing letter listed on your BOM provides important information that you should be aware of before you install HP DCE. Some of this information may not be included in either this guide or the release notes.

HP DCE provides online release notes. Read the release notes before you install the product. They contain information about changes to the product.

1.3 Troubleshooting

The HP DCE for OpenVMS Alpha and OpenVMS I64 Product Guide includes a chapter on troubleshooting. Read this chapter if you are having installation or configuration problems. For example, the Troubleshooting chapter discusses problems you may encounter with time and time zones.

1.4 Installation Procedure Requirements

The following sections discuss the requirements for installing HP DCE.

The length of time the installation takes to complete depends on the type of machine, the load on that machine, and the kit you choose to install.

1.4.1 Required Hardware

To perform the installation, you need the following hardware:

A processor running OpenVMS I64 Version 8.2 or OpenVMS Alpha Version 7.3-2 or higher.
A software distribution device, if you are installing the software from media. You need a distribution device that corresponds with the software distribution media.

Note

Systems running OpenVMS Alpha should have access to a CD-ROM reader so you can install the software. Please check to see that you have a CD-ROM reader installed.

1.4.2 Required Software

This section describes the software that must be installed on an OpenVMS system before you can properly perform the installation, configure the system, or use the software. In cases where the minimum version is not specified, refer to the Software Product Description (SPD) for more information.

1.4.2.1 On OpenVMS Alpha and I64 Systems

Before installing HP DCE, you need the following software on your system:

OpenVMS I64 Version 8.2 or OpenVMS Alpha Version 7.3-2 or higher.
DECnet Phase IV or DECnet/OSI
DECnet is required only if you run applications that use DECnet as their transport.
HP TCP/IP Services Version 5.0 or higher
You must have HP TCP/IP Services installed and configured on each host from which you plan to execute DCE applications. See HP TCP/IP Services for OpenVMS Installation and Configuration for more information about the UDP/IP and TCP/IP transports.
If you plan to use MultiNet or TCPware from Process Software (instead of HP's TCP/IP Services for OpenVMS), please see the release notes for more information.
If you are installing the Application Developer's Kit and plan on using the LSE templates, LSE and an appropriate license must be installed before you install DCE.

1.4.3 Time Required for Installation

Depending on your configuration, the installation can take from 10 to 30 minutes.

1.4.4 Disk Space, Global Pages, and Global Sections Required

The disk space, global pages, and global sections requirements of HP DCE are different for the DCE Runtime Services Kit (RTK) and for the Application Developer's Kit (ADK). These requirements also differ on OpenVMS Alpha and on OpenVMS I64 systems. Table 1-1 lists the requirements before the installation for each kit on each platform. (Disk space requirements are listed in blocks.) Note that the DCE CDS Server and Security Server images are part of the DCE Kit and are enabled by license PAKs.

Table 1-1 Disk Space, Global Pages, and Global Sections Requirements
Kit Disk Space Global Pages Global Sections

OpenVMS Alpha RTK 48,000 7350 35

OpenVMS Alpha RTK & ADK 58,000 7350 35

OpenVMS I64 RTK 101,000 17,500 90

OpenVMS I64 RTK & ADK 113,000 17,500 90

**Table 1-1 Disk Space, Global Pages, and Global Sections Requirements**
Kit	Disk Space	Global Pages	Global Sections
OpenVMS Alpha RTK	48,000	7350	35
OpenVMS Alpha RTK & ADK	58,000	7350	35
OpenVMS I64 RTK	101,000	17,500	90
OpenVMS I64 RTK & ADK	113,000	17,500	90

To determine how much free disk space is on your system disk, enter the following command:

$ SHOW DEVICE SYS$SYSDEVICE

The system responds with a short table; the column labeled Free Blocks shows the amount of storage space remaining on your system disk. If there is not enough disk space to install or to run HP DCE, work with your system manager to delete and purge files that are no longer needed.

To determine the number of free global pages and global sections on your system, enter the following commands:

$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")

$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")

If the values displayed by the system are greater than the minimum required, your system has adequate free global pages and global sections. If the values are less than the minimum required, use the AUTOGEN command procedure to increase the values, as follows:

$ EDIT SYS$SYSTEM:MODPARAMS.DAT

For details on using AUTOGEN, see the HP OpenVMS System Manager's Manual.

1.4.5 Privileges and Quotas Required

To install HP DCE for OpenVMS Alpha and OpenVMS I64, log in to the system manager account. If you are not logged in to the system manager's account during installation, you must have at least the SETPRV privilege. To determine the privileges you have, enter the following command:

$ SHOW PROCESS/PRIVILEGES

If you do not have sufficient privileges to install HP DCE, see your system manager.

The DCE system management utility requires WORLD privileges for the SHOW command and WORLD, SYSPRV, and CMKRNL privileges for all other commands.

You should also check to make sure you have adequate quotas for the installation. You need the following quota values:

ASTLM = 24
BIOLM = 18
BYTLM = 18000
DIOLM = 18
ENQLM = 30
FILLM = 20

Use the OpenVMS Authorize Utility if you want to verify and change process quotas for the installation account in the user authorization file (UAF). For example, to change the BYTLM quota for your installation account, enter the following command sequence:

$ RUN SYS$SYSTEM:AUTHORIZE UAF> MODIFY account-name /BYTLM = 18000 UAF> SHOW account-name UAF> EXIT $ LOGOUT

After you change the quotas for your installation account, log out of the installation account and log in again for the new quotas to take effect. You can then proceed with the installation.

User account quotas are stored in the file SYSUAF.DAT. For more information on modifying account quotas, see the description of the Authorize Utility in the OpenVMS system management documentation.

1.4.6 Completing License Management Facility Requirements

If you are installing only the Runtime Services Kit of HP DCE, you do not need a separate license. The right to use the HP DCE Runtime Services Kit is granted with the OpenVMS operating system.

The installation procedure for DCE installs the following kits by default without checking for licenses: DCE Runtime Services, CDS Server Kit, and the Security Server Kit. To install the Application Developer's Kit, you must override the installation defaults by answering NO to the following question:

Do you want the defaults for all options? [YES]

If you are installing the Application Developer's Kit and plan on using LSE templates, LSE and an appropriate license must be installed before you install DCE.

To register a license under OpenVMS, first log in to the system manager's account, SYSTEM. Then use either of two ways to perform the registration:

Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK.
At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information.

The license for the Application Developer's Kit is DCE-APP-DEV. The license for the Security Server Kit is DCE-SECURITY. The license for the CDS Server Kit is DCE-CDS.

Although it is necessary to have only one license active for this product, the License Management Facility (LMF) checks for the existence of any valid license. If LMF displays license failures for some of these other licenses, disregard the messages.

If you plan to use HP DCE on more than one node in a VMScluster environment, you must register and load a license for each of the other nodes before you configure them.

For complete information about using LMF, see the HP OpenVMS License Management Utility Manual.

Contents

Index

Internet	openvmsdoc@hp.com
Postal Mail	Hewlett-Packard Company OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698

Ctrl/ x	A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
italic text	Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where device-name contains up to five alphanumeric characters).
UPPERCASE TEXT	Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
`Monospace text`	Monospace text indicates code examples and interactive screen displays. In the C programming language, monospace text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.
Case-sensitivity	OpenVMS operating system commands do not differentiate between uppercase and lowercase. However, many DCE commands do make this distinction. In particular, the system configuration utility interprets names in a case-sensitive manner.