Back up your system disk before installing any software. Use the backup procedures established at your site. For details on backing up a system disk, see the OpenVMS Backup Utility Manual.

1.4.8 Installing DCE Version 1.5 Over Previous Versions

If you are installing DCE over an existing DIGITAL DCE for OpenVMS VAX or OpenVMS Alpha Version 1.5, perform the following steps:

1. Stop the DCE deamons with the following commands:

   $ @SYS$MANAGER:DCE$SETUP CLEAN

   $ @SYS$MANAGER:DCE$RPC_SHUTDOWN

2. After the installation, enter the following command:

   $ @SYS$MANAGER:DCE$SETUP START

This chapter describes the installation procedure for Digital DCE for OpenVMS VAX and OpenVMS Alpha.

You can use different media to install Digital DCE. The examples in this chapter show the installation procedure using disk files.

See Appendix B for logs of sample installations.

2.1 About the OpenVMS Installation Procedure

This section gives a brief overview of the OpenVMS installation procedure for DCE Version 1.5 called DCE$INSTALL.COM. The OpenVMS installation command has the following format:

$ @DKA300:[000000]DCE$INSTALL [HELP]

where:

• DKA300: is a device name on which the distribution volumes will be mounted. Remember that all Alpha systems come with CD-ROM readers.
• DCE$INSTALL is the supplied command procedure that drives the installation.

It is not necessary to use the console drive to install DCE. If you do use the console drive, replace any media you remove from the drive.

Include the optional parameter HELP if you want PCSI to display help information.

When you invoke DCE$INSTALL, it checks the following conditions:

• Whether you are logged in to a privileged account. Install software from the system manager's account with your default device and directory set to SYS$UPDATE.
• Whether you have adequate quotas for installation. See Section 1.4.5 for more information on quota values.

You can stop the installation at any time by pressing Ctrl/C or Ctrl/Y. However, files created up to that point are not deleted. You must delete these files manually, using the OpenVMS DELETE command. Appendix A lists the files and directories created during the installation procedure.

2.2 Starting the Digital DCE Installation Procedure

See Section 1.4.2 for more information about software requirements.

Start the installation procedure as follows:

1. Log in to the account from which you are installing the Digital DCE.
2. If you are installing a kit other than the Run Time Services Kit, make sure you have registered the appropriate LMF PAK.
3. Invoke the following command procedure, substituting the correct name of your media device and directory for DKA300 (used in the example):

   $ @DKA300:[000000]DCE$INSTALL HELP

This section describes the part of the installation procedure that is specific to DCE.

$ @DKA300:[000000]dce$install help Performing DCE pre-installation tasks...please wait.

Creating a DCE$SERVER Account

If you do not already have a DCE$SERVER account, the installation procedure creates one for you with TMPMBX, NETMBX, DETACH, and SYSPRV privileges.

This installation procedure has detected an existing DCE$SERVER account. Correct operation of DCE on this system requires that the DCE$SERVER account have TMPMBX, NETMBX, DETACH and SYSPRV privileges. The installation procedure will modify the DCE$SERVER account to ensure that the prerequisite privileges are present. %UAF-I-MDFYMSG, user record(s) updated The following product has been selected: DEC AXPVMS DCE V1.5 Layered Product [Installed] Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS DCE V1.5: DCE V1.5 for OpenVMS Alpha

Description of Kits

The installation procedure displays information about the four Digital DCE kits (Run Time Services Kit, Application Developer's Kit, Security Server Kit, and CDS Server Kit). Depending on the kit, the procedure displays specific information about the kit that will be installed.

Greetings! This is DCE V1.5 for OpenVMS Alpha. There are four components: the DCE Runtime Services, the DCE Application Development Kit, the DCE Security Server, and the DCE CDS Server. 1. The Runtime Services provides the core services necessary to execute and manage DCE applications. 2. The Application Development Kit provides the services and tools required to develop, execute, and manage DCE applications. The Runtime Services capability is automatically provided with the Application Development Kit. 3. The security server supplies support for a cell wide security database. A cell must have at least one system running a security server. 4. The CDS server supplies support for a cell wide naming database. A cell must have at least one system running a CDS server. © Digital Equipment Corporation. 1995,1998. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Digital Equipment Corporation The software product is sold by Digital Equipment Corporation. This product uses the following PAKS: DCE-SECURITY, DCE-CDS, DCE-APP-DEV This product currently has 3 Product Authorization Keys: Producer PAK Name Version Release Date DEC DCE-SECURITY V1.5 01-JUN-1995 DEC DCE-CDS V1.5 01-JUN-1995 DEC DCE-APP-DEV V1.5 01-JUN-1995 Do you want the defaults for all options? [YES] NO The Application Development Kit is optional and enabled with a PAK. It provides the services and tools required to develop, execute, and manage DCE applications. The Application Development Kit installs: + Required DCE application development header files + Interface Definition Language Compiler (IDL) + Language-Sensitive Editor (LSE) Templates for the Interface Definition Language + Unique User Identifier (UUID) Generator + Sample DCE Applications The Application Development Kit [NO] YES Do you want to review the options? [NO] Execution phase starting ... The following product will be installed to destination: DEC AXPVMS DCE V1.5 DISK$SYSTEM:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS DCE V1.5 Layered Product *** DCE Product installation successful...beginning post-installation. The rights identifier NET$DECLAREOBJECT will now be granted to the DCE$SERVER account. You may IGNORE the message: "%UAF-E-GRANTERR, unable to grant identifier NET$DECLAREOBJECT to DCE$SERVER-SYSTEM-F-DUPIDENT, duplicate identifier" if it should occur. Press return to Continue %UAF-E-GRANTERR, unable to grant identifier NET$DECLAREOBJECT to DCE$SERVER-SYSTEM-F-DUPIDENT, duplicate identifier

Installing Language Sensitive Editor (LSE) Templates for IDL

If you are installing DCE on a cluster on which the Language Sensitive Editor (LSE) is installed, the system or the user must have a license to run LSE in order for DCE to install the LSE templates for the Interface Definition Language (IDL) compiler. Type YES to the following question if you have a license to run LSE.

Load the Language-Sensitive Editor (LSE) templates for IDL? [Y]: NO NOTE: Please add the following to your system's SYS$MANAGER:SYLOGIN.COM. These files define foreign commands for using DCE on OpenVMS. $ @SYS$MANAGER:DCE$DEFINE_REQUIRED_COMMANDS.COM $ @SYS$COMMON:[DCE$LIBRARY]DCE$DEFINE_OPTIONAL_COMMANDS.COM

Selecting a TCP/IP Product

You are now asked to update DCE$STARTUP.COM and choose a TCP/IP product.

Please add the following command to SYS$STARTUP:SYSTARTUP_*.COM on your system. This ensures that DCE$STARTUP.COM is executed at system boot. The parameters supplied to DCE$STARTUP.COM depend on the specific TCP/IP product you intend to use. You will now be asked to select the name of this TCP/IP product, and the installation will supply you with the correct command for SYS$STARTUP:SYSTARTUP_*.COM. TCP/IP product Keyword Digital's TCP/IP Services for OpenVMS UCX Multinet from TGV MULTINET Pathway from Wollongong PATHWAY TCPware from Process Software TCPWARE No TCP/IP Available at this time NONE Enter one of the keywords from the table above [UCX]:

See the release notes for more information on UCX, MultiNet, Pathway, and TCPware.

Enter $ @SYS$STARTUP:DCE$STARTUP in your SYS$STARTUP:SYSTARTUP_*.COM %DCE-W-INSTALL, Please increase the sysgen parameter GBLPAGES to 118171 %DCE-S-INSTALL, Installation of OpenVMS DCE V1.5 completed

2.4 Installing on a VMScluster

On a VMScluster with a common system disk, you need only install Digital DCE once. After the initial installation, ensure that a separate license is registered and loaded on each cluster member that you plan to use for DCE services.

If you are installing DCE for OpenVMS over an existing version of DCE on a common system disk in a VMScluster environment, be sure to shut down DCE on all nodes that share the common system disk before the installation.

To configure each node separately, enter the following command on each node:

$ @SYS$MANAGER:DCE$SETUP.COM CONFIG

If you are installing Digital DCE on a VMScluster that does not have a common system disk, you must install and configure on each node that you plan to use for DCE services.

This chapter describes postinstallation steps that you need to take and lists ways to recover from errors that you encounter during the installation.

3.1 Postinstallation Tasks

After the installation is completed successfully, note the following.

1. DCE Version 1.5 provides support for the RPC Runtime environment and RPC applications (which are not dependent on DCE services) to remain active when DCE is shut down. This requires the use of separate startup files: SYS$STARTUP:DCE$RPC_STARTUP.COM and SYS$STARTUP:DCE$STARTUP.COM.
   On OpenVMS VAX and Alpha Version 7.2, the RPC Runtime environment files are shipped with the operating system, and are not provided when DCE is installed. When installing DCE Version 1.5 on OpenVMS VAX and Alpha Version 6.1 through 7.1, DCE provides the RPC runtime environment files.
   If you want all of the configured DCE services to start with the system startup, add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM after the startup commands for the network transports, DECnet, and/or DEC TCP/IP Services:

   $ @SYS$STARTUP:DCE$STARTUP.COM

   
   If you want only the RPC Runtime environment to start with the system startup, add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:

   $ @SYS$STARTUP:DCE$RPC_STARTUP.COM

   
   It is not necessary to run both procedures. Invoking DCE$STARTUP.COM will first start the RPC Runtime, then the DCE services. See Chapter 4 for more information about configuring DCE.

2. Depending on your choice for system startup, add the following commands to SYS$MANAGER:SYSHUTDWN.COM before the shutdown commands for the network transports, DECnet, and/or DEC TCP/IP Services:
   • If you have configured DCE services on your system:

     $ @SYS$STARTUP:DCE$SHUTDOWN.COM

     $ @SYS$STARTUP:DCE$RPC_SHUTDOWN.COM NOCONFIRM

   • If you have the RPC run-time environment only:

     $ @SYS$STARTUP:DCE$RPC_SHUTDOWN.COM NOCONFIRM

3. Configure this node by entering the following command:

   $ @SYS$MANAGER:DCE$SETUP CONFIG

   
   You must configure the DCE services before you can use them. See Chapter 4 for more information about configuring DCE.

4. If you are running DCE server applications that are listening over the DECnet Phase IV (ncacn_dnet_nsp) protocol or the DECnet/OSI (ncacn_dnet_nsp) protocol, you must grant the NET$DECLAREOBJECT rights identifier to those processes from which the server runs.
5. Define foreign commands. There are two foreign command definition files: one file contains required commands and the other file is optional. Add the following line to the file SYS$MANAGER:SYLOGIN.COM:

   $ @SYS$MANAGER:DCE$DEFINE_REQUIRED_COMMANDS.COM

   
   DCE$DEFINE_REQUIRED_COMMANDS.COM, the required command definition file, defines the following foreign commands:

   • acl_edit, which invokes the ACL editor (Security)
   • cdscp, which invokes the CDS control program
   • chpass, which invokes the DCE change password utility
   • DCE$UAF, which invokes the DCE Integrated Login User Authorization File utility
   • dce_login, which validates a principal's identity and obtains network credentials (Security)
   • dtscp, which invokes the DTS control program
   • EXPORT, which invokes the DCE Integrated Login EXPORT utility
   • IMPORT, which invokes the DCE Integrated Login IMPORT utility
   • kdestroy, which destroys a principal's login context (Security)
   • kinit, which obtains a ticket-granting ticket (Security)
   • klist, which lists tickets (Security)
   • rgy_edit, which invokes the registry database editor (Security)
   • rpccp, which invokes the RPC control program
   
   If you choose not to execute this command definition file, you cannot use any of the previous programs and commands.
   DCE$DEFINE_OPTIONAL_COMMANDS.COM, the optional command definition file, defines the following foreign commands:
   • idl, which invokes the IDL compiler
   • nidl_to_idl, which invokes the utility that converts from NIDL to IDL
   • rpclm, which invokes the RPC Log Manager
   • uuidgen, which invokes the UUID generator utility
   
   By default, these utilities use DCL-style interfaces. If you execute the optional foreign commands file, you have access to the version of these utilities that uses the universal interface. There are three possible actions that you can take:
   • Define the universal interface for all users on your system to ensure that the same interface is available to users across operating system platforms. Note that all examples that document these four utilities use the universal interface. Include the following line in the file SYS$MANAGER:SYLOGIN.COM:

     $ @SYS$COMMON:[DCE$LIBRARY]DCE$DEFINE_OPTIONAL_COMMANDS.COM

   • Give users access to only the DCL-style interface. In this case, you do not need to take any action.
   • Make the DCL-style interface available to some users, but allow others access to the universal interface. Do not define the optional commands in SYLOGIN.COM. Tell users who want to use the universal interface to include the following line in their account's LOGIN.COM procedure:

     $ @SYS$COMMON:[DCE$LIBRARY]DCE$DEFINE_OPTIONAL_COMMANDS.COM

6. If you are installing DCE on a VMScluster, you must take the following steps:
   1. Ensure that a license is registered and loaded on each node in the cluster from which users plan to use DCE. (If you are installing only the Digital DCE Run Time Services Kit, you already have a right to use the DCE Run Time Services Kit. This right was granted with the OpenVMS operating system license.)
   2. Configure each node in the cluster from which users plan to use DCE by entering the following command:

      $ @SYS$MANAGER:DCE$SETUP CONFIG

The following list describes errors that you may encounter during installation and provides suggestions about how to recover from those errors:

• You try to install the OpenVMS VAX kit on an OpenVMS Alpha system (or vice versa).
  Reinstall with the correct kit.
• The system does not have the required version of OpenVMS installed.
  Upgrade the operating system to at least the minimum required version and restart the installation procedure.
• You run out of disk space.
  Either clean up your disk or install less of the kit.
• If you plan to run DCE applications via IP, you must have UCX Version 4.1A installed.
  Install the correct version of UCX. The installation procedure checks for the prerequisites.
• No network transports were found.
  You must install and configure DECnet, UCX, or both before running any DCE applications.
• SYS$SYSTEM:RIGHTSLIST.DAT does not exist on this system.
  RUN AUTHORIZE and then issue the CREATE/RIGHTS command. RIGHTSLIST.DAT is created for you.
• Invalid UIC.
  Find and enter the correct UIC in the correct format.