COM, Registry, and Events for OpenVMS Developer's Guide

Document revision date: 15 July 2002

COM, Registry, and Events for OpenVMS Developer's Guide

Contents

Index

4.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 Compaq 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:

Edit the SYLOGICALS.COM file to stop the following products from starting:
- OpenVMS Registry (comment the line DEFINE/SYSTEM REG$TO_BE_STARTED TRUE )
- COM for OpenVMS (comment the line DEFINE DCOM$TO_BE_STARTED TRUE )
Edit the SYS$STARTUP:SYSTARTUP_VMS.COM file to stop the following products from starting:
- Compaq 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, Compaq Advanced Server for OpenVMS (if running), and then the OpenVMS Registry on all nodes in the cluster.

Use the following procedure:

Upgrade to OpenVMS Version 7.2-1 or higher on all required system disks. For this procedure, see the OpenVMS Alpha Version 7.x Upgrade and Installation Manual.
Upgrade TCP/IP. For this procedure, see the Compaq TCP/IP Services for OpenVMS Installation and Configuration manual or your TCP/IP supplier's documentation.
Boot the upgraded system from the system disk.
Upgrade to COM Version 1.2 for OpenVMS. For this procedure, see Section 4.9.

Upgrade Compaq Advanced Server for OpenVMS on this node in the cluster. For this procedure, see the Compaq Advanced Server for OpenVMS Server Installation and Configuration Guide.

Note

You must install Compaq Advanced Server for OpenVMS on at least one Alpha node in the cluster. On the other nodes, you can either install Compaq Advanced Server for OpenVMS or select External Authentication images (only) .

Configure TCP/IP (set up for startup on reboot on each node). You must configure the PWIP driver for Compaq Advanced Server for OpenVMS to use TCP/IP. For information about configuring TCP/IP, see the Compaq TCP/IP Services for OpenVMS Installation and Configuration manual or your TCP/IP supplier's documentation.
Configure the OpenVMS Registry as follows:
- Run REG$CONFIG.COM to configure the OpenVMS Registry. See Section 13.2. You need to configure the OpenVMS Registry only once for the cluster.
- 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
Configure and start Compaq Advanced Server for OpenVMS. For this procedure, see the Compaq Advanced Server for OpenVMS Server Installation and Configuration Guide.
If this node is running Compaq Advanced Server for OpenVMS, set up Compaq 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 Compaq Advanced Server for OpenVMS, edit the SYLOGICALS.COM file and define the PWRK$ACME_SERVER logical. For this procedure, see the Compaq Advanced Server for OpenVMS Server Installation and Configuration Guide. For more information about the PWRK$ACME_SERVER logical, see Table 8-2.
Start the ACME server. Use the following command:
$ @SYS$STARTUP:NTA$STARTUP_NT_ACME
Start RPC. Use the following command:
$ @SYS$STARTUP:DCE$RPC_STARTUP.COM
See Appendix D for detailed information about upgrading from COM Version 1.0 for OpenVMS to COM Version 1.2 for OpenVMS.
Configure COM for OpenVMS. For this procedure, see Section 4.10 and Section 6.2.
- Populate the OpenVMS Registry. For this procedure, see Section 6.2. Use option 3 to populate the OpenVMS Registry database. You need to populate the OpenVMS Registry only once in a cluster.
- Create any OpenVMS and Compaq Advanced Server for OpenVMS accounts needed by the COM for OpenVMS Service Control Manager. For more information, see Section 6.2. Use option 8 to create the accounts. You need to create these accounts only once in a cluster.
Edit the SYLOGICALS.COM file and add the following line:
$ DEFINE DCOM$TO_BE_STARTED TRUE
Start COM for OpenVMS on a particular node. For this procedure, see Section 4.11.

4.8 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 4.3.

Figure 4-1 shows the relationships and dependencies of the processes and operating system layers.

Figure 4-1 Interrelationships Among Processes and Layers

Table 4-1 lists the process names and maps each name to its corresponding server.

Table 4-1 Process Name to Server Name Mapping
Process name Server name For more information

DCOM$RPCSS COM for OpenVMS Service Control Manager (SCM) Section 4.8.1

REGISTRY_SERVER OpenVMS Registry server Section 4.8.2

PWRK xxx Compaq Advanced Server for OpenVMS server (multiple processes) Section 4.8.3

ACME_SERVER ACME server Section 4.8.4

DCE$RPCD RPC endpoint mapper Section 4.8.5

**Table 4-1 Process Name to Server Name Mapping**
Process name	Server name	For more information
DCOM$RPCSS	COM for OpenVMS Service Control Manager (SCM)	Section 4.8.1
REGISTRY_SERVER	OpenVMS Registry server	Section 4.8.2
PWRK xxx	Compaq Advanced Server for OpenVMS server (multiple processes)	Section 4.8.3
ACME_SERVER	ACME server	Section 4.8.4
DCE$RPCD	RPC endpoint mapper	Section 4.8.5

The following sections list and describe the servers and the layers.

4.8.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

Configured by: DCOM$SETUP. See Section 6.2.

Started by: DCOM$SETUP, option 4. See Section 6.2.

Shutdown procedure: DCOM$SETUP, option 5. See Section 6.2.

4.8.2 OpenVMS Registry Server

The OpenVMS Registry server manages the OpenVMS Registry database.

Process name: REGISTRY_SERVER

Requires: None.

Required by: COM for OpenVMS, Compaq Advanced Server for OpenVMS

Configured by: REG$CONFIG. See Section 13.2.

Started by: REG$STARTUP. See Section 13.3.1.

Shutdown procedure: SET SERVER REGISTRY_SERVER/EXIT. For more information, see Section 13.4.

4.8.3 Compaq Advanced Server for OpenVMS Server

The Compaq 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$LMMCP
PWRK$LMSRV
PWRK$MASTER
PWRK$MONITOR
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 Compaq PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide.

4.8.4 ACME Server

The ACME server controls the granting of credentials.

Process name: ACME_SERVER

Requires: Compaq Advanced Server for OpenVMS

Required by: OpenVMS (RPC and SSPI/NTLM layers) and OpenVMS Events

Started:

Automatically when the SYLOGICALS.COM file contains the following line: NTA$NT_ACME_TO_BE_STARTED YES
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 Section 8.3.2.

4.8.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 Compaq DCE for OpenVMS VAX and OpenVMS Alpha manual.

4.8.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

4.8.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 Chapter 15.

4.9 Installing COM for OpenVMS

The COM for OpenVMS installation kit contains a single POLYCENTER Software Installation utility file. The name of the kit is DEC-AXPVMS-DCOM-V0102--1.PCSI . You must install the COM for OpenVMS files on an OpenVMS Alpha system. Please check the prerequisites before installing the kit. See Section 4.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 no longer required

The COM for OpenVMS MIDL compiler no longer requires the DCOM-MIDL license.

Example 4-1 shows a sample installation.

Example 4-1 Sample COM for OpenVMS Installation

$ product install dcom/source=disk:[directory] The following product has been selected: DEC AXPVMS DCOM V1.2 Layered Product 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.2 Copyright 2002 Compaq Information Technologies Group, L.P. 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 higher - Includes DCE RPC and OpenVMS Registry - TCP/IP Services for OpenVMS V5.0 or later (or equivalent product) - Advanced Server for OpenVMS V7.3 or later 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.2 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.2 Layered Product $

4.10 COM for OpenVMS Postinstallation Procedures

After you install the COM for OpenVMS kit, do the following:

Verify that the OpenVMS Registry is running. (See Chapter 13.)
Verify that the Compaq Advanced Server for OpenVMS is running. (See Section 4.8.3 for the Compaq Advanced Server for OpenVMS process names.)
Verify that the ACME server is running. (See Section 4.8.4 for the name of this process.)
Verify that the RPC daemon is running. (See Section 4.8.5 for the name of the process.)
Populate the OpenVMS Registry with the required COM for OpenVMS keys and values using the DCOM$SETUP utility, option 3. (See Section 6.2.) You must do this only once in an OpenVMS Cluster.
Configure the DCOM$RPCSS account using the DCOM$SETUP utility, option 8. (See Section 6.2.1.) You must do this only once in an OpenVMS Cluster.
Start COM for OpenVMS using the DCOM$SETUP utility, option 4. (See Section 6.2.) You must do this on every node in an OpenVMS Cluster.
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 4.11.1.) You must do this on every node in an OpenVMS Cluster.
Configure COM for OpenVMS security. See Chapter 5.

4.11 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 Section 6.2.)

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:

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]

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 ***

4.11.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

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 Section 6.2).

4.12 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 Section 6.2.)

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:

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 ***

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]?

Enter Y to continue with the shutdown procedure.

Note

For information about suppressing this confirmation step, see Section 4.12.1.

The system displays the following messages:

Terminating DCOM Service Control Manager daemon (DCOM$RPCSS) . . . *** DCOM shutdown successful *** *** DCOM Shutdown Procedure Complete ***

If the COM for OpenVMS Service Control Manager is initializing on this node, the system shuts down the process as follows:

Terminating DCOM Service Control Manager daemon (DCOM$STARTUP-**) . . . *** DCOM shutdown successful *** *** DCOM Shutdown Procedure Complete ***

4.12.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:

*** DCOM system shutdown procedure *** Terminating DCOM Service Control Manager daemon (DCOM$RPCSS) . . . *** DCOM shutdown successful *** *** DCOM Shutdown Procedure Complete ***

Contents

Index

privacy and legal statement

6539PRO_003.HTML