____________________________________________________ COM for OpenVMS Installation Guide July 1999 This document contains instructions on installing COM Version 1.1 for OpenVMS. Revision/Update Information: This is an updated manual. Software Version: OpenVMS Alpha Version 7.2-1 Microsoft Windows NT 4.0 SP3 Compaq Computer Corporation Houston, Texas ________________________________________________________________ July 1999 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital Equipment Corporation or an authorized sublicensor. © Digital Equipment Corporation 1999. All rights reserved. This product includes software licensed from Microsoft Corporation. Copyright © Microsoft Corporation, 1991-1997. All rights reserved. This product includes software licensed from Bristol Technology, Inc. Copyright © Bristol Technology, Inc, 1990-1997. All rights reserved. Compaq, the Compaq logo, and the DIGITAL logo are registered in the U.S. Patent and Trademark Office. Alpha, AlphaServer, AlphaStation, DEC, DIGITAL, OpenVMS, POLYCENTER, Tru64, VAX, VMS, are trademarks of Compaq Computer Corporation. COMPAQ, the Compaq logo, and the DIGITAL logo are registered in the U. S. Patent and Trademark Office. The following are third-party trademarks: Microsoft, MS, MS-DOS, Win32, Windows, and Windows NT are registered trademarks, and NT, Windows 95, and Windows 98 are trademarks of Microsoft Corporation. Adobe, Display POSTSCRIPT, and POSTSCRIPT are registered trademarks of Adobe Systems Incorporated. Apple, Mac, Macintosh, and Power Macintosh are registered trademarks of Apple Computer, Inc. AT&T is a registered trademark of the American Telephone and Telegraph Company. Compaq is a registered trademark of Compaq Computer Corporation. Motif, OSF/1, UNIX and the "X" device are registered trademarks, and IT DialTone, X/Open, and The Open Group are trademarks, of The Open Group in the U.S. and other countries. Unicode is a registered trademark of Unicode, Inc. Wind/U is a registered trademark of Bristol Technology, Inc. Other product names mentioned herein may be the trademarks of their respective companies. - The Compaq OpenVMS documentation set is available on CD-ROM. 25-JUN-1999 13:09:03.96 _________________________________________________________________ Contents Preface................................................... v 1 Installing the COM for OpenVMS Kit 1.1 Contents of the COM Version 1.1 for OpenVMS Kit........................................... 1-1 1.2 Prerequisites................................. 1-1 1.3 Supported COM for OpenVMS Installations....... 1-2 1.4 Installing COM for OpenVMS on an OpenVMS Standalone System............................. 1-3 1.5 Upgrading from COM Version 1.0 for OpenVMS on an OpenVMS Standalone System.................. 1-5 1.6 Installing COM for OpenVMS on an OpenVMS Cluster....................................... 1-8 1.7 Upgrading COM for OpenVMS in an OpenVMS Cluster....................................... 1-11 1.8 OpenVMS External Authentication............... 1-14 1.8.1 LOGINOUT.EXE Use of External Authentication............................ 1-15 1.8.2 DCE Integrated Login Restriction.......... 1-15 1.9 Understanding the COM for OpenVMS Environment................................... 1-16 1.9.1 COM for OpenVMS Service Control Manager (SCM)..................................... 1-16 1.9.2 OpenVMS Registry Server................... 1-17 1.9.3 Advanced Server for OpenVMS Server........ 1-17 1.9.4 ACME Server............................... 1-18 1.9.5 RPC Endpoint Mapper....................... 1-19 1.9.6 RPC and SSPI/NTLM Layers.................. 1-19 1.9.7 OpenVMS Events............................ 1-19 1.10 Installing COM for OpenVMS.................... 1-20 1.11 COM for OpenVMS Postinstallation Procedures... 1-21 iii 1.12 Starting COM for OpenVMS (COM for OpenVMS Service Control Manager)...................... 1-22 1.12.1 Starting COM for OpenVMS Automatically after a Reboot............................ 1-23 1.13 Shutting Down COM for OpenVMS (COM for OpenVMS Service Control Manager)...................... 1-24 1.13.1 Suppressing the DCOM$SHUTDOWN Confirmation Request................................... 1-25 Index Examples 1-1 Sample COM for OpenVMS Installation....... 1-21 Tables 1-1 Process Name to Server Name Mapping....... 1-16 iv _________________________________________________________________ Preface Related Documents For additional information on the Open Systems Software Group (OSSG) products and services, access the Compaq OpenVMS World Wide Web site with the following address: www.compaq.com/openvms Reader's Comments Compaq welcomes your comments on this manual. Print or edit the online form SYS$HELP:OPENVMSDOC_ COMMENTS.TXT and send us your comments by: Internet openvmsdoc@compaq.com Fax 603 884-0120, Attention: OSSG Documentation, ZKO3-4/U08 Mail OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation Use the following World-Wide Web address to order additional documentation: www.compaq.com/openvms To reach the OpenVMS documentation website, click the Documentation link. If you need help deciding which documentation best meets your needs, call 800-ATCOMPAQ. v Conventions In this manual, any reference to OpenVMS is synonymous with Compaq OpenVMS. VMScluster systems are now referred to as OpenVMS Cluster systems. Unless otherwise specified, references to OpenVMS Clusters or clusters in this document are synonymous with VMSclusters. In this manual, every use of DECwindows and DECwindows Motif refers to DECwindows Motif for OpenVMS software. The following conventions are also used in this manual: 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. PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button. In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box. . . . A horizontal ellipsis in examples indicates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. vi . A vertical ellipsis indicates the omission . of items from a code example or command . format; the items are omitted because they are not important to the topic being discussed. ( ) In command format descriptions, parentheses indicate that you must enclose the options in parentheses if you choose more than one. [ ] In command format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification or in the syntax of a substring specification in an assignment statement.) [|] In command format descriptions, vertical bars separating items inside brackets indicate that you choose one, none, or more than one of the options. { } In command format descriptions, braces indicate required elements; you must choose one of the options listed. text style This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason. In the HTML version of this document, this convention appears as italic text. 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 dd represents the predefined code for the device type). vii 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 type indicates code examples and Monospace type interactive screen displays. In the C programming language, monospace type in 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. - A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line. numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. viii 1 _________________________________________________________________ Installing the COM for OpenVMS Kit This chapter provides a list of the contents of the COM for OpenVMS kit, a list of prerequisite software, and preinstallation requirements. It also describes how to install COM for OpenVMS and includes postinstallation instructions. 1.1 Contents of the COM Version 1.1 for OpenVMS Kit COM Version 1.1 for OpenVMS contains the following: o Software - COM for OpenVMS Run-Time libraries - COM for OpenVMS MIDL compiler and header files - COM for OpenVMS configuration utilities - Sample applications o Documentation - OpenVMS Connectivity Developer Guide (in PostScript, HTML, and PDF formats) 1.2 Prerequisites The following software is required: o For OpenVMS systems - OpenVMS Version 7.2-1 or higher - DEC C Version 5.6 or higher and DEC C++ Version 5.6 or higher (for COM for OpenVMS application development) - DIGITAL TCP/IP Services for OpenVMS Version 5.0 or equavalent - Advanced Server for OpenVMS Version 7.2A or higher Installing the COM for OpenVMS Kit 1-1 Installing the COM for OpenVMS Kit 1.2 Prerequisites - Before installing COM for OpenVMS check that you have the required free global pages, global sections, and disk blocks. The following table lists the requirements. _____________________________________________________ Global Global Software_________pages_______sections____Disk_blocks_ COM for OpenVMS 11,000 27 57000 RPC_Runtime______3,300_______14__________N/A_________ Advanced Server: See the Advanced Server for OpenVMS Server Installation and Configuration Guide. TCP/IP: See the DIGITAL TCP/IP Services for OpenVMS: Installation and Configuration document. o For Windows[R] NT[TM] systems - Windows NT 4.0 with Service Pack 3 installed - Microsoft[R] Visual C++ (for Windows NT client development and information about MIDL compiler). See the Microsoft website for compiler version requirements. - TCP/IP enabled (needed for OpenVMS connectivity) 1.3 Supported COM for OpenVMS Installations The following sections describe COM Version 1.1 for OpenVMS installation and upgrade options: 1-2 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.3 Supported COM for OpenVMS Installations ___________________________________________________________ If_you_want_to_do_this__________Read_this_section__________ Install COM for OpenVMS on an See Section 1.4. OpenVMS standalone system for the first time. Install COM for OpenVMS on an See Section 1.6. OpenVMS Cluster system for the first time. Upgrade from COM Version 1.0 See Section 1.5. for OpenVMS to COM Version 1.1 for OpenVMS on an OpenVMS standalone system. Upgrade from COM Version 1.0 See Section 1.7. for OpenVMS to COM Version 1.1 for OpenVMS on an OpenVMS Cluster_system.____________________________________________ 1.4 Installing COM for OpenVMS on an OpenVMS Standalone System Use the following procedure: 1. Install OpenVMS Version 7.2-1. For this procedure, see the OpenVMS Alpha Version 7.x Upgrade and Installation Manual. 2. Install TCP/IP. For this procedure, see the DIGITAL TCP/IP Services for OpenVMS: Installation and Configuration manual or your TCP/IP supplier's documentation. 3. Boot the installed system from the system disk. 4. Install COM Version 1.1 for OpenVMS. For this procedure, see Section 1.10. 5. Install Advanced Server for OpenVMS. For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. 6. Configure TCP/IP (set up for startup and reboot); start TCP/IP. For this procedure, see the DIGITAL TCP/IP Services for OpenVMS: Installation and Configuration manual or your TCP/IP supplier's documentation. Installing the COM for OpenVMS Kit 1-3 Installing the COM for OpenVMS Kit 1.4 Installing COM for OpenVMS on an OpenVMS Standalone System 7. Configure the OpenVMS Registry as follows: o Run REG$CONFIG to configure the OpenVMS Registry. See See Section 9.2 in the OpenVMS Connectivity Developer Guide. o Edit the SYLOGICALS.COM file to define the SYS$REGISTRY logical as follows: $ DEFINE/SYSTEM SYS$REGISTRY directory-specification 8. Start OpenVMS Registry by running the REG$STARTUP.COM file. 9. If you want to run DCE, start DCE now. ________________________ Note ________________________ You do not need DCE to run COM for OpenVMS, but if your environment uses DCE, Compaq recommends that you start DCE now. ______________________________________________________ For this procedure, see the DIGITAL DCE Installation and Configuration Guide. For more information about OpenVMS external authentication, see Section 1.8. 10.Configure Advanced Server for OpenVMS. You need to reboot to finish Advanced Server for OpenVMS configuration. You must reboot 0 to n times, depending on your system configuration. For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. 11.Start Advanced Server for OpenVMS (set up for startup on reboot). For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. 12.Start the ACME server. Use the following command: $ @SYS$STARTUP:NTA$STARTUP_NT_ACME 13.Start RPC. Use the following command: $ @SYS$STARTUP:DCE$RPC_STARTUP.COM 1-4 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.4 Installing COM for OpenVMS on an OpenVMS Standalone System 14.Configure COM for OpenVMS. For this procedure, see Section 1.11 and the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. o Populate the OpenVMS Registry. For this procedure, see the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Use option 3 to populate the OpenVMS Registry database. o Create any OpenVMS and Advanced Server for OpenVMS accounts needed by the COM for OpenVMS Service Control Manager. For more information, see the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Use option 8 to create the accounts. 15.Edit the SYLOGICALS.COM file and add the following line: $ DEFINE DCOM$TO_BE_STARTED TRUE 16.Start COM for OpenVMS. For this procedure, see Section 1.12. 1.5 Upgrading from COM Version 1.0 for OpenVMS on an OpenVMS Standalone System ________________________ Note ________________________ Before you start, Compaq recommends that you disable any Advanced Server for OpenVMS, OpenVMS Registry, and layered products automatic startups so these products do not start until you have upgraded COM for OpenVMS and its associated components. Use the following procedure: o Edit the SYLOGICALS.COM file to stop the following products from starting: - OpenVMS Registry (remove the line DEFINE REG$TO_ BE_STARTED TRUE or DEFINE/SYSTEM REG$TO_BE_ STARTED TRUE) - COM for OpenVMS (comment the line DEFINE DCOM$TO_BE_STARTED TRUE) Installing the COM for OpenVMS Kit 1-5 Installing the COM for OpenVMS Kit 1.5 Upgrading from COM Version 1.0 for OpenVMS on an OpenVMS Standalone System o Edit the SYS$STARTUP:SYSTARTUP_VMS.COM file to stop the following products from starting: - Advanced Server for OpenVMS (comment the line @SYS$STARTUP:PWRK$STARTUP.COM). If COM for OpenVMS is currently running, shut down COM for OpenVMS first, Advanced Server for OpenVMS (if running), and then the OpenVMS Registry. ______________________________________________________ Use the following procedure: 1. Upgrade to OpenVMS Version 7.2-1. For this procedure, see the OpenVMS Alpha Version 7.x Upgrade and Installation Manual. 2. If you need to upgrade TCP/IP, upgrade TCP/IP now. For this procedure, see the DIGITAL TCP/IP Services for OpenVMS: Installation and Configuration manual or your TCP/IP supplier's documentation. 3. Boot the upgraded system from the system disk. 4. Upgrade COM for OpenVMS. For this procedure, see Section 1.10. 5. Install or upgrade Advanced Server for OpenVMS. You must reboot 0 to n times, depending on your system configuration. For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. 6. Start TCP/IP unless you have enabled TCP/IP to start on a reboot. For this procedure, see the DIGITAL TCP/IP Services for OpenVMS: Installation and Configuration manual or your TCP/IP supplier's documentation. 7. Start the OpenVMS Registry unless you have enabled the OpenVMS Registry to start on a reboot. For this procedure, see See Section 9.2 in the OpenVMS Connectivity Developer Guide. 1-6 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit from COM Version 1.0 for OpenVMS on an OpenVMS Standalone System 8. If you want to run DCE, start DCE now. ________________________ Note ________________________ You do not need DCE to run COM for OpenVMS, but if your environment uses DCE, Compaq recommends that you start DCE now. ______________________________________________________ For this procedure, see the DIGITAL DCE Installation and Configuration Guide. For more information about OpenVMS external authentication, see Section 1.8. 9. Configure Advanced Server for OpenVMS. You must reboot to finish Advanced Server for OpenVMS configuration. You need to reboot 0 to n times, depending on your system configuration. For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. 10.Start Advanced Server for OpenVMS (set up for startup on reboot). For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. 11.Start the ACME server. Use the following command: $ @SYS$STARTUP:NTA$STARTUP_NT_ACME 12.Start RPC. Use the following command: $ @SYS$STARTUP:DCE$RPC_STARTUP.COM 13.See See Addendix D in the OpenVMS Connectivity Developer Guide for detailed information about upgrading from COM Version 1.0 for OpenVMS to COM Version 1.1 for OpenVMS. 14.Configure COM for OpenVMS. For this procedure, see Section 1.11 and the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. o Populate the OpenVMS Registry. For this procedure, see the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Use option 3 to populate the OpenVMS Registry database. Installing the COM for OpenVMS Kit 1-7 Installing the COM for OpenVMS Kit 1.5 Upgrading from COM Version 1.0 for OpenVMS on an OpenVMS Standalone System o Create any OpenVMS and Advanced Server for OpenVMS accounts needed by the COM for OpenVMS Service Control Manager. For more information, see the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Use option 8 to create the accounts. 15.Edit the SYLOGICALS.COM file and add the following line: $ DEFINE DCOM$TO_BE_STARTED TRUE 16.Start COM for OpenVMS. For this procedure, see Section 1.12. 1.6 Installing COM for OpenVMS on an OpenVMS Cluster ________________________ Note ________________________ This cluster installation procedure assumes you are installing COM for OpenVMS on a single system disk. ______________________________________________________ Use the following procedure: 1. Install OpenVMS Version 7.2-1 on all system disks as required. For this procedure, see the OpenVMS Alpha Version 7.x Upgrade and Installation Manual. 2. Install TCP/IP. For this procedure, see the DIGITAL TCP/IP Services for OpenVMS: Installation and Configuration manual or your TCP/IP supplier's documentation. 3. Boot the installed system from the system disk. 4. Install COM Version 1.1 for OpenVMS. For this procedure, see Section 1.10. 5. Install Advanced Server for OpenVMS on this node in the cluster. For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. ________________________ Note ________________________ You must install Advanced Server for OpenVMS on at least one Alpha node in the cluster. On the other nodes, you can either install Advanced Server for 1-8 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.6 Installing COM for OpenVMS on an OpenVMS Cluster OpenVMS or select External Authentication images (only). ______________________________________________________ 6. Configure TCP/IP (set up for startup on reboot on each node) and start TCP/IP. For this procedure, see the DIGITAL TCP/IP Services for OpenVMS: Installation and Configuration manual or your TCP/IP supplier's documentation. 7. Configure the OpenVMS Registry: o Run REG$CONFIG to configure the OpenVMS Registry. You need to configure the OpenVMS Registry only once for the cluster. See See Section 9.2 in the OpenVMS Connectivity Developer Guide. o Set the SYS$REGISTRY logical to DEFINE/SYSTEM on every Alpha node in the cluster that will run the OpenVMS Registry server. o Edit the SYLOGICALS.COM file on every node in the cluster as follows: - If the cluster uses a single, cluster-common SYLOGICALS.COM file that is called by each node's SYLOGICALS.COM file, you do not need to make any changes. - On those nodes where you do not want the OpenVMS Registry server to run, add the following line to the SYLOGICALS.COM file: $ DEFINE/SYSTEM REG$TO_BE_STARTED FALSE Advanced Server for OpenVMS requires that the OpenVMS Registry be running on a node in the cluster. 8. Configure DCE. ________________________ Note ________________________ You do not need DCE to run COM for OpenVMS, but if your environment uses DCE, Compaq recommends that you start DCE now. ______________________________________________________ Installing the COM for OpenVMS Kit 1-9 Installing the COM for OpenVMS Kit 1.6 Installing COM for OpenVMS on an OpenVMS Cluster For this procedure, see the DIGITAL DCE Installation and Configuration Guide. 9. If you want to run DCE, start DCE now. You must configure DCE on each node on which you want to run DCE. For more information about OpenVMS external authentication, see Section 1.8. 10.Configure and start Advanced Server for OpenVMS. For this procedure, see the Advanced Server for OpenVMS /Server Installation and Configuration Guide. If this node is running Advanced Server for OpenVMS, set up Advanced Server for OpenVMS for startup on reboot (edit the SYS$STARTUP file as necessary). You must reboot 0 to n times as needed, depending on your system configuration. If this node is not running Advanced Server for OpenVMS, edit the SYLOGICALS.COM file and define the PWRK$ACME_ SERVER logical. For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. For more information about the PWRK$ACME_SERVER logical, see See Chapter 13 in the OpenVMS Connectivity Developer Guide. 11.Start the ACME server. Use the following command: $ @SYS$STARTUP:NTA$STARTUP_NT_ACME 12.Start RPC. Use the following command: $ @SYS$STARTUP:DCE$RPC_STARTUP.COM 13.Configure COM for OpenVMS. For this procedure, see Section 1.11 and the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. o Populate the OpenVMS Registry. For this procedure, see the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Use option 3 to populate the OpenVMS Registry database. You need to populate the OpenVMS Registry only once in a cluster. 1-10 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.6 Installing COM for OpenVMS on an OpenVMS Cluster o Create any OpenVMS and Advanced Server for OpenVMS accounts needed by the COM for OpenVMS Service Control Manager. For more information, see the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Use option 8 to create the accounts. You need to create these accounts only once in a cluster. 14.Edit the SYLOGICALS.COM file and add the following line: $ DEFINE DCOM$TO_BE_STARTED TRUE 15.Start COM for OpenVMS. For this procedure, see Section 1.12. 1.7 Upgrading COM for OpenVMS in an OpenVMS Cluster ________________________ Note ________________________ This cluster upgrade procedure assumes you are installing COM for OpenVMS on a single system disk. ______________________________________________________ ________________________ Note ________________________ Before you start, Compaq recommends that you disable any Advanced Server for OpenVMS and layered products automatic startups so these products do not start until you have upgraded COM for OpenVMS and its associated components. Use the following procedure: o Edit the SYLOGICALS.COM file to stop the following products from starting: - OpenVMS Registry (remove the line DEFINE REG$TO_ BE_STARTED TRUE or DEFINE/SYSTEM REG$TO_BE_ STARTED TRUE) - COM for OpenVMS (comment the line DEFINE DCOM$TO_BE_STARTED TRUE) o Edit the SYS$STARTUP:SYSTARTUP_VMS.COM file to stop the following products from starting: - Advanced Server for OpenVMS (comment the line @SYS$STARTUP:PWRK$STARTUP.COM) Installing the COM for OpenVMS Kit 1-11 Installing the COM for OpenVMS Kit 1.7 Upgrading COM for OpenVMS in an OpenVMS Cluster If COM for OpenVMS is currently running, shut down COM for OpenVMS first, Advanced Server for OpenVMS (if running), and then the OpenVMS Registry on all nodes in the cluster. ______________________________________________________ Use the following procedure: 1. Upgrade to OpenVMS Version 7.2-1 on all required system disks. For this procedure, see the OpenVMS Alpha Version 7.x Upgrade and Installation Manual. 2. Upgrade TCP/IP. For this procedure, see the DIGITAL TCP/IP Services for OpenVMS: Installation and Configuration manual or your TCP/IP supplier's documentation. 3. Boot the upgraded system from the system disk. 4. Upgrade to COM Version 1.1 for OpenVMS. For this procedure, see Section 1.10. 5. Upgrade Advanced Server for OpenVMS on this node in the cluster. For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. ________________________ Note ________________________ You must install Advanced Server for OpenVMS on at least one Alpha node in the cluster. On the other nodes, you can either install Advanced Server for OpenVMS or select External Authentication images (only). ______________________________________________________ 6. Configure TCP/IP (set up for startup on reboot on each node). For this procedure, see the DIGITAL TCP/IP Services for OpenVMS: Installation and Configuration manual or your TCP/IP supplier's documentation. 7. Configure the OpenVMS Registry as follows: o Run REG$CONFIG to configure the OpenVMS Registry. See See Section 9.2 in the OpenVMS Connectivity Developer Guide. You need to configure the OpenVMS Registry only once for the cluster. 1-12 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.7 Upgrading COM for OpenVMS in an OpenVMS Cluster o Edit the SYLOGICALS.COM file on every node that will run the OpenVMS Registry server to define the SYS$REGISTRY logical. For example: $ DEFINE/SYSTEM SYS$REGISTRY cluster-visible-directory-specification Edit the SYLOGICALS.COM file on every node in the cluster as follows: - If the cluster uses a single, cluster-common SYLOGICALS.COM file that is called by each node's SYLOGICALS.COM file, you do not need to make any changes. - On those nodes where you do not want the OpenVMS Registry server to run, add the following line to the SYLOGICALS.COM file: $ DEFINE/SYSTEM REG$TO_BE_STARTED FALSE 8. Configure and start Advanced Server for OpenVMS. For this procedure, see the Advanced Server for OpenVMS /Server Installation and Configuration Guide. If this node is running Advanced Server for OpenVMS, set up Advanced Server for OpenVMS for startup on reboot (edit the SYS$STARTUP file as necessary). You must reboot 0 to n times as needed, depending on your system configuration. If this node is not running Advanced Server for OpenVMS, edit the SYLOGICALS.COM file and define the PWRK$ACME_ SERVER logical. For this procedure, see the Advanced Server for OpenVMS/Server Installation and Configuration Guide. For more information about the PWRK$ACME_SERVER logical, see See Chapter 13 in the OpenVMS Connectivity Developer Guide. 9. Start the ACME server. Use the following command: $ @SYS$STARTUP:NTA$STARTUP_NT_ACME 10.Start RPC. Use the following command: $ @SYS$STARTUP:DCE$RPC_STARTUP.COM 11.See See Addendix D in the OpenVMS Connectivity Developer Guide for detailed information about upgrading from COM Version 1.0 for OpenVMS to COM Version 1.1 for OpenVMS. Installing the COM for OpenVMS Kit 1-13 Installing the COM for OpenVMS Kit 1.7 Upgrading COM for OpenVMS in an OpenVMS Cluster 12.Configure COM for OpenVMS. For this procedure, see Section 1.11 and the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. o Populate the OpenVMS Registry. For this procedure, see the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Use option 3 to populate the OpenVMS Registry database. You need to populate the OpenVMS Registry only once in a cluster. o Create any OpenVMS and Advanced Server for OpenVMS accounts needed by the COM for OpenVMS Service Control Manager. For more information, see the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Use option 8 to create the accounts. You need to create these accounts only once in a cluster. 13.Edit the SYLOGICALS.COM file and add the following line: $ DEFINE DCOM$TO_BE_STARTED TRUE 14.Start COM for OpenVMS on a particular node. For this procedure, see Section 1.12. 1.8 OpenVMS External Authentication COM for OpenVMS uses NTLM security credentials to control access to COM objects. OpenVMS users can use the NTA$LOGON utility, a user interface to the Authentication and Credential Management (ACM) Authority, to authenticate a Windows NT user defined by the Advanced Server for OpenVMS (PATHWORKS) facility and acquire the necessary credentials. Authentication on OpenVMS requires that the Windows NT username maps to a local OpenVMS account in the SYSUAF.DAT file. By default, external (NTLM) authentication requires that you set the EXTAUTH flag for the OpenVMS account that maps to the Windows NT username. If you do not set the EXTAUTH flag, OpenVMS cannot perform the required mapping. If the flag is not set, authentication fails. 1-14 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.8 OpenVMS External Authentication For example, if the Advanced Server for OpenVMS (PATHWORKS) user database defines a Windows NT username SMITH and the host mapping database defines a correspondence between a Windows NT username SMITH and an OpenVMS account called JSMITH, the SYSUAF.DAT record for JSMITH on the OpenVMS system must have the EXTAUTH flag enabled. If the EXTAUTH flag is not enabled or if the host mapping entry for the Windows NT username is deleted, external authentication fails. You can remove the requirement that every OpenVMS account used for external authentication have the EXTAUTH flag set by setting the IGNORE_EXTAUTH flag (bit 11, %X0800) in the SECURITY_POLICY sysgen parameter. When you enable the IGNORE_EXTAUTH flag, an OpenVMS user can use the NTA$LOGON utility to acquire credentials even if the Windows NT username maps to an OpenVMS account that does not have the EXTAUTH flag enabled. 1.8.1 LOGINOUT.EXE Use of External Authentication The EXTAUTH flag also directs LOGINOUT.EXE to use external authentication to authenticate an OpenVMS user during the login process (that is, local, dialup, remote, interactive, and network logins). When you set the EXTAUTH flag, LOGINOUT.EXE uses external authentication to verify the OpenVMS username and password-not the password in the SYSUAF.DAT record. LOGINOUT external authentication always requires that you set the EXTAUTH flag in the SYSUAF account record. Unlike NTA$LOGON and authenticated RPC, this requirement cannot be overriden using the IGNORE_EXTAUTH flag. 1.8.2 DCE Integrated Login Restriction A site cannot use both External Authentication and the older LGI-callout feature on the same system. If you have an LGI-callout image installed, External Authentication is disabled for login purposes. Because DCE Integrated Login uses the LGI-callout mechanism, OpenVMS will not allow logins using Windows NT-based external authentication if DCE Integrated Login is enabled. Installing the COM for OpenVMS Kit 1-15 Installing the COM for OpenVMS Kit 1.9 Understanding the COM for OpenVMS Environment 1.9 Understanding the COM for OpenVMS Environment COM for OpenVMS relies on a number of interrelated servers (processes) and operating system images. In most cases, the servers start automatically when you restart the system. (Automatic startup requires that you have installed and configured each component and have made appropriate changes to the SYLOGICALS.COM file.) For more information about starting and configuring the servers, see Section 1.3. Figure 1-1 shows the relationships and dependencies of the processes and operating system layers. Table 1-1 lists the process names and maps each name to its corresponding server. Table_1-1_Process_Name_to_Server_Name_Mapping______________ Process_name__Server_name___________For_more_information___ DCOM$RPCSS COM for OpenVMS Section 1.9.1 Service Control Manager (SCM) REGISTRY_ OpenVMS Registry Section 1.9.2 SERVER server PWRKxxx Advanced Server Section 1.9.3 for OpenVMS server (multiple processes) ACME_SERVER ACME server Section 1.9.4 DCE$RPCD______RPC_endpoint_mapper___Section_1.9.5__________ The following sections list and describe the servers and the layers. 1.9.1 COM for OpenVMS Service Control Manager (SCM) The COM for OpenVMS Service Control Manager enables COM for OpenVMS. Process name: DCOM$RPCSS Requires: OpenVMS Registry, OpenVMS (RPC and SSPI/NTLM layers) Required by: COM applications 1-16 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.9 Understanding the COM for OpenVMS Environment Configured by: DCOM$SETUP. See the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Started by: DCOM$SETUP, option 4. See the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. Shutdown procedure: DCOM$SETUP, option 5. See the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide. 1.9.2 OpenVMS Registry Server The OpenVMS Registry server manages the OpenVMS Registry database. Process name: REGISTRY_SERVER Requires: None. Required by: COM for OpenVMS, Advanced Server for OpenVMS Configured by: REG$CONFIG. See See Section 9.2 in the OpenVMS Connectivity Developer Guide. Started by: REG$STARTUP. See See Section 9.3.1 in the OpenVMS Connectivity Developer Guide. Shutdown procedure: SET SERVER REGISTRY_SERVER/EXIT. For more information, see See Section 9.4 in the OpenVMS Connectivity Developer Guide. 1.9.3 Advanced Server for OpenVMS Server The Advanced Server for OpenVMS server provides Windows NT and OpenVMS connectivity. Process names: NETBIOS PWRK$ADMIN_0 PWRK$KNBDAEMON PWRK$LICENSE_R PWRK$LMBROWSER PWRK$LMDMN PWRK$LMMCP PWRK$LMSRV PWRK$MASTER PWRK$MONITOR Installing the COM for OpenVMS Kit 1-17 Installing the COM for OpenVMS Kit 1.9 Understanding the COM for OpenVMS Environment PWRK$NBDAEMON The ACME server requires the PWRK$LMSRV process specifically. Requires: OpenVMS Registry Required by: ACME server Configured by: PWRK$CONFIG Started by: PWRK$STARTUP Shutdown procedure: PWRK$SHUTDOWN For more information, see the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. 1.9.4 ACME Server The ACME server controls the granting of credentials. Process name: ACME_SERVER Requires: Advanced Server for OpenVMS Required by: OpenVMS (RPC and SSPI/NTLM layers) and OpenVMS Events Started: o Automatically when the SYLOGICALS.COM file contains the following line: NTA$NT_ACME_TO_BE_STARTED YES o You can also start the ACME server manually by entering the following command: $ @SYS$STARTUP:NTA$STARTUP_NT_ACME Shutdown procedure: $ SET SERVER ACME {/EXIT | /ABORT} For more information, see See Section 13.3.3 in the OpenVMS Connectivity Developer Guide. 1-18 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.9 Understanding the COM for OpenVMS Environment 1.9.5 RPC Endpoint Mapper The RPC endpoint mapper controls authentication and security. Process name: DCE$RPCD Requires: RPC image Required by: COM for OpenVMS Service Control Manager, RPC image Started by: OpenVMS Shutdown procedure: Use the following command procedure: $ @SYS$STARTUP:DCE$RPC_SHUTDOWN.COM For more information, see the DIGITAL DCE for OpenVMS VAX and OpenVMS Alpha manual. 1.9.6 RPC and SSPI/NTLM Layers The RPC and SSPI/NTLM layers provides remote procedure call and Windows NT-style authentication on OpenVMS. Process name: n/a (part of OpenVMS operating system) Requires: OpenVMS, ACME server Required by: COM for OpenVMS Started by: OpenVMS Shutdown procedure: n/a 1.9.7 OpenVMS Events The Events layer provides Windows NT-style event logging on OpenVMS. Process name: n/a (part of OpenVMS operating system) Requires: ACME server Required by: COM for OpenVMS Started by: OpenVMS Shutdown procedure: n/a For more information, see See Chapter 12 in the OpenVMS Connectivity Developer Guide. Installing the COM for OpenVMS Kit 1-19 Installing the COM for OpenVMS Kit 1.10 Installing COM for OpenVMS 1.10 Installing COM for OpenVMS The COM for OpenVMS installation kit contains a single POLYCENTER Software Installation file. The name of the kit is DEC-AXPVMS-DCOM-V0101--1.PCSI. You must install the COM for OpenVMS files on an OpenVMS Alpha Version 7.2-1 system. Please check the prerequisites before installing the kit. See Section 1.2. To install COM for OpenVMS, invoke the POLYCENTER Software Installation utility using the following command: $ PRODUCT INSTALL /SOURCE=device:[user] DCOM For device:[user], specify the device name and directory location of the kit, respectively. ________________ MIDL compiler license ________________ The COM for OpenVMS MIDL compiler requires a license. Compaq provides the DCOM-MIDL PAK separately from the COM for OpenVMS kit. ______________________________________________________ Example 1-1 shows a sample installation. 1-20 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.10 Installing COM for OpenVMS Example 1-1 Sample COM for OpenVMS Installation $ product install dcom/source=disk:[directory] The following product has been selected: DEC AXPVMS DCOM V1.1 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 DCOM V1.1 Copyright Compaq Computer Corporation 1999. All rights reserved. Do you want the defaults for all options? [YES] The following software is required to run COM for OpenVMS - OpenVMS Alpha V7.2-1 or later - Includes DCE RPC and OpenVMS Registry - TCP/IP Services for OpenVMS V5.0 or later (or equivalent product) - Advanced Server for OpenVMS V7.2A or later - In order to use the DCOM MIDL compiler you must install the DCOM-MIDL License PAK Do you want to continue? [YES] Do you want to review the options? [NO] Execution phase starting ... The following product will be installed to destination: DEC AXPVMS DCOM V1.1 DISK$AXP_72PLUS:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS DCOM V1.1 Layered Product $ 1.11 COM for OpenVMS Postinstallation Procedures After you install the COM for OpenVMS kit, do the following: 1. Verify that the OpenVMS Registry is running. (See the OpenVMS Registry System Management chapter in the Installing the COM for OpenVMS Kit 1-21 Installing the COM for OpenVMS Kit 1.11 COM for OpenVMS Postinstallation Procedures OpenVMS Connectivity Developer Guide or OpenVMS System Manager Manual.) 2. Verify that the Advanced Server for OpenVMS is running. (See Section 1.9.3 for the Advanced Server for OpenVMS process names.) 3. Verify that the ACME server is running. (See Section 1.9.4 for the name of this process.) 4. Verify that the RPC daemon is running. (See Section 1.9.5 for the name of the process.) 5. Populate the OpenVMS Registry with the required COM for OpenVMS keys and values using the DCOM$SETUP utility, option 3. (See the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide.) You must do this only once on an OpenVMS cluster. 6. Configure the DCOM$RPCSS account using the DCOM$SETUP utility, option 8. (See See Section 6.2.1 in the OpenVMS Connectivity Developer Guide.) You must do this only once on an OpenVMS cluster. 7. Start COM for OpenVMS using the DCOM$SETUP utility, option 4. (See the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide.) You must do this on every node in an OpenVMS cluster. 8. If you want COM for OpenVMS to start automatically when the system reboots, modify the DEFINE DCOM$TO_BE_STARTED line in the SYLOGICALS.COM file. (See Section 1.12.1.) You must do this on every node in an OpenVMS cluster. 1.12 Starting COM for OpenVMS (COM for OpenVMS Service Control Manager) Use the following command to start COM for OpenVMS: $ @SYS$STARTUP:DCOM$STARTUP Alternately, you can run DCOM$SETUP and choose option 4. (See the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide.) 1-22 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit 1.12 Starting COM for OpenVMS (COM for OpenVMS Service Control Manager) The COM for OpenVMS Service Control Manager can be in one of the following states: initializing/running or not started. Depending on the COM for OpenVMS Service Control Manager state, you will see one of the following messages: o If the COM for OpenVMS Service Control Manager is running on this node, the system reports that the process is already active: DCOM Service Control Manager daemon (DCOM$RPCSS) is active [pid=xxxxxxxx] If the COM for OpenVMS Service Control Manager is initializing on this node, the system reports that the process is already active: DCOM Service Control Manager daemon (DCOM$STARTUP-**) is active [pid=xxxxxxxx] o If the COM for OpenVMS Service Control Manager is not started on this node, the system starts COM for OpenVMS as follows: The OpenVMS Registry server is already started on this node. *** DCOM system startup procedure *** Starting DCOM Service Control Manager daemon ( "DCOM$STARTUP-**" ) . . . After initialization, the daemon will use process name "DCOM$RPCSS" . . . %RUN-S-PROC_ID, identification of created process is xxxxxxxx *** DCOM startup successful *** *** DCOM Startup Procedure Complete *** 1.12.1 Starting COM for OpenVMS Automatically after a Reboot Compaq recommends that you modify the SYS$MANAGER:SYLOGICALS.COM command file to control COM for OpenVMS startup. OpenVMS includes a revised SYLOGICALS.TEMPLATE file that includes new startup commands for COM for OpenVMS and related components. Review the "Coordinated Startup" section of this template file and add the appropriate information to your existing startup files. To have COM for OpenVMS start automatically when the system boots, copy the following line to your SYLOGICALS.COM file, uncomment the line, and make sure it is set to TRUE: $ DEFINE DCOM$TO_BE_STARTED TRUE Installing the COM for OpenVMS Kit 1-23 Installing the COM for OpenVMS Kit 1.12 Starting COM for OpenVMS (COM for OpenVMS Service Control Manager) If you do not set COM for OpenVMS to start automatically when the system boots, you can start COM for OpenVMS using the DCOM$SETUP OpenVMS COM Tools menu, option 4 (see the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide). 1.13 Shutting Down COM for OpenVMS (COM for OpenVMS Service Control Manager) Use the following command to shut down COM for OpenVMS: $ @SYS$STARTUP:DCOM$SHUTDOWN Alternately, you can run DCOM$SETUP and choose option 5. (See the DCOM$SETUP utility section (Chapter 6) in the OpenVMS Connectivity Developer Guide.) The COM for OpenVMS Service Control Manager can be in one of the following states: stopped, running, or initializing. Depending on the COM for OpenVMS Service Control Manager state, you will see one of the following messages: o If the COM for OpenVMS Service Control Manager is stopped on this node, the system reports that there is nothing to shut down: *** DCOM system shutdown procedure *** There is no active DCOM$RPCSS daemon on this system. *** DCOM Shutdown Procedure Complete *** o If the COM for OpenVMS Service Control Manager is running on this node, the system shuts down the process as follows: *** DCOM system shutdown procedure *** *************************** Warning ******************************** *** Stopping the DCOM Service Control Manager daemon (DCOM$RPCSS) *** Active DCOM applications will no longer be operational. Do you want to proceed with this operation (YES/NO/?) [N]? 1-24 Installing the COM for OpenVMS Kit Installing the COM for OpenVMS Kit Shutting Down COM for OpenVMS (COM for OpenVMS Service Control Manager) Enter Y to continue with the shutdown procedure. ________________________ Note ________________________ For information about suppressing this confirmation step, see Section 1.13.1. ______________________________________________________ The system displays the following messages: Terminating DCOM Service Control Manager daemon (DCOM$RPCSS) . . . *** DCOM shutdown successful *** *** DCOM Shutdown Procedure Complete *** o If the COM for OpenVMS Service Control Manager is initializing on this node, the system shuts down the process as follows: *** DCOM system shutdown procedure *** *************************** Warning ******************************** *** Stopping the DCOM Service Control Manager daemon (DCOM$RPCSS) *** Active DCOM applications will no longer be operational. Do you want to proceed with this operation (YES/NO/?) [N]? Enter Y to continue with the shutdown procedure. The system displays the following messages: Terminating DCOM Service Control Manager daemon (DCOM$STARTUP-**) . . . *** DCOM shutdown successful *** *** DCOM Shutdown Procedure Complete *** 1.13.1 Suppressing the DCOM$SHUTDOWN Confirmation Request You can suppress the DCOM$SHUTDOWN command confirmation request by specifying the NOCONFIRM parameter. Use the following command: $ @SYS$STARTUP:DCOM$SHUTDOWN NOCONFIRM The system displays the following shutdown messages without prompting you to confirm the shutdown: Installing the COM for OpenVMS Kit 1-25 Installing the COM for OpenVMS Kit 1.13 Shutting Down COM for OpenVMS (COM for OpenVMS Service Control Manager) *** DCOM system shutdown procedure *** Terminating DCOM Service Control Manager daemon (DCOM$RPCSS) . . . *** DCOM shutdown successful *** *** DCOM Shutdown Procedure Complete *** 1-26 Installing the COM for OpenVMS Kit _________________________________________________________________ Index A______________________________ M______________________________ ACM authority, 1-14 Modifying the SYLOGICALS file D for COM for OpenVMS, 1-23 _______________________________ DCOM$TO_BE_STARTED logical, N______________________________ 1-23 NTA$LOGON, 1-14 NTLM authentication, 1-14 E______________________________ NTLM security credentials, EXTAUTH flag, 1-14 1-14 External authentication, 1-14 S______________________________ I______________________________ SECURITY_POLICY sysgen IGNORE_EXTAUTH flag, 1-15 parameter, 1-15 Shutting down COM for OpenVMS, L______________________________ 1-24 LOGINOUT.EXE, 1-15 NOCONFIRM parameter, 1-25 Index-1