Previous | Contents | Index |
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 DIGITAL DCE for OpenVMS VAX or OpenVMS Alpha Version 1.5 over a previous version of DCE, you do not have to reconfigure DCE after the installation. Before the installation, stop the DCE deamons with the following command:
Then, after the installation, enter the following command:
You must reconfigure if you are installing DCE for the first time or if you are installing a new version over DCE Version 1.0. |
If you are installing DCE over an existing DIGITAL DCE for OpenVMS VAX or OpenVMS Alpha Version 1.5, perform the following steps:
$ @SYS$MANAGER:DCE$SETUP CLEAN |
$ @SYS$MANAGER:DCE$RPC_SHUTDOWN |
$ @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:
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:
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:
$ @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. |
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 |
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 |
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 |
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.
You must configure each node separately. A reboot is also required. |
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.
$ @SYS$STARTUP:DCE$STARTUP.COM |
$ @SYS$STARTUP:DCE$RPC_STARTUP.COM |
$ @SYS$STARTUP:DCE$SHUTDOWN.COM |
$ @SYS$STARTUP:DCE$RPC_SHUTDOWN.COM NOCONFIRM |
$ @SYS$STARTUP:DCE$RPC_SHUTDOWN.COM NOCONFIRM |
$ @SYS$MANAGER:DCE$SETUP CONFIG |
$ @SYS$MANAGER:DCE$DEFINE_REQUIRED_COMMANDS.COM |
$ @SYS$COMMON:[DCE$LIBRARY]DCE$DEFINE_OPTIONAL_COMMANDS.COM |
$ @SYS$COMMON:[DCE$LIBRARY]DCE$DEFINE_OPTIONAL_COMMANDS.COM |
$ @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:
Previous | Next | Contents | Index |