Document revision date: 19 July 1999

!!Caution!! When the OpenVMS Registry server starts, the system creates an OpenVMS Registry database at this location. If you already have an OpenVMS Registry database on your system, you must redefine the SYS$REGISTRY logical to point to that location. Do you wish to create the directory? (Y/N/Q) [Y]:

If you enter Y, the system confirms the directory creation.

The SYS$REGISTRY directory has now been created. Press [Enter] to return to the menu.

4.2 Starting the OpenVMS Registry

You can control how the OpenVMS Registry starts as follows:

• Start the OpenVMS Registry automatically when the system reboots.
• Have products that require the OpenVMS Registry to be running start the OpenVMS Registry.
• Start the OpenVMS Registry manually.
• Prevent the OpenVMS Registry from starting.

Use the OpenVMS Registry Configuration utility described in Section 4.1 to control how the OpenVMS Registry starts.

4.2.1 Starting the OpenVMS Registry Manually

Under some conditions, you might want to start the OpenVMS Registry server manually.

Compaq recommends that you use the SYS$STARTUP:REG$STARTUP.COM command procedure. This command procedure ensures that the server process quotas are set to the required minimum values.

Example 4-1 shows an example of how to start the OpenVMS Registry using the SYS$STARTUP:REG$STARTUP.COM command procedure.

Example 4-1 OpenVMS Registry Manual Startup Procedure

$ @SYS$STARTUP:REG$STARTUP.COM

Alternately, you can use the following command to start the OpenVMS Registry manually:

$ SET SERVER REGISTRY_SERVER/START

4.3 Shutting Down the OpenVMS Registry

The OpenVMS Registry server is shut down automatically as part of a system shutdown.

If you want to shut down the OpenVMS Registry manually, use the following command:

$ SET SERVER REGISTRY_SERVER/EXIT

4.4 OpenVMS Registry Server Commands

The OpenVMS Registry server commands allow you to display (SHOW) and change (SET) the state of the OpenVMS Registry server. The following sections list and describe the OpenVMS Registry server commands.

Show the current status of the OpenVMS Registry on a specified node.

This command requires the SYSPRV privilege.

Format

SHOW SERVER REGISTRY_SERVER

[/MASTER | /CLUSTER | /NODE=(node ,...)]

[/PAGE]

Qualifiers

/MASTER

Displays the node and process ID (PID) of the current OpenVMS Registry master server in the cluster. This command does not communicate with the OpenVMS Registry servers in the cluster. Requires SYSLCK privilege as well as the SYSPRV privilege.

/CLUSTER

Returns the show output from each OpenVMS Registry server in the cluster, listing the OpenVMS Registry master server information first.

/NODE=(node,...)]

Returns OpenVMS Registry server information about the servers on the specified nodes, listed in the order in which you enter the node names. The node names you specify must be in the current cluster.

/PAGE

Displays the returned show output in a scrollable page display.

Change the state of the OpenVMS Registry.

This command requires the SYSPRV privilege.

Format

SET SERVER REGISTRY_SERVER

[/MASTER | /CLUSTER | /NODE=(node ,...)]

[/START | /RESTART | /EXIT | /ABORT ]

[/[NO]LOG ]

Qualifiers

/MASTER

Issues the specified command to the OpenVMS Registry master server only. Requires the SYSLCK privilege as well as the SYSPRV privilege.

/CLUSTER

Issues the SET command to each OpenVMS Registry server in the cluster, setting the OpenVMS Registry master server last.

/NODE=(node,...)

Issues the SET command to the OpenVMS Registry servers on the specified nodes, in the order in which you enter the node names. The node names must be in the current cluster.

/START[=(node,...)]

Starts the OpenVMS Registry server on the specified node or nodes in the cluster.

/EXIT[=(node,...)]

Stops the OpenVMS Registry server on the specified node or nodes in the cluster.

/ABORT[=(node,...)]

Aborts the OpenVMS Registry server on the specified node or nodes in the cluster.

/[NO]LOG

Creates a new OpenVMS Registry log file in SYS$REGISTRY. NOLOG is the default.

4.5 OpenVMS Registry Failover in a Cluster

When you run more than one OpenVMS Registry server in a cluster, only one OpenVMS Registry server process is active and writing to the OpenVMS Registry database. The other OpenVMS Registry server processes are standing by.

By default, the first OpenVMS Registry server process that is active in the cluster remains active until either the process no longer exists or the priority among OpenVMS Registry server processes changes.

4.5.1 Changing the Priority of OpenVMS Registry Server Processes

You can change the priority of OpenVMS Registry server processes by creating and modifying the priority value of each node in the cluster that will run the OpenVMS Registry server process: the higher the value, the higher the priority.

Example 4-2 shows priority values being assigned so that NODENAME1 will be the active OpenVMS Registry server process in the cluster.

Example 4-2 Setting Priority Values

$ mcr reg$cp REG> CREATE VALUE HKEY_LOCAL_MACHINE\SYSTEM\REGISTRY\PRIORITY - _REG> /NAME=NODENAME1/DATA=15/TYPE=DWORD REG> CREATE VALUE HKEY_LOCAL_MACHINE\SYSTEM\REGISTRY\PRIORITY - _REG> /NAME=NODENAME2/DATA=10/TYPE=DWORD REG> CREATE VALUE HKEY_LOCAL_MACHINE\SYSTEM\REGISTRY\PRIORITY - _REG> /NAME=NODENAME3/DATA=5/TYPE=DWORD

In Example 4-2, if NODENAME1 shuts down, control of the OpenVMS Registry database passes to the server process on NODENAME2.

Example 4-3 shows the system manager increasing the priority value of NODENAME3 to 20.

Example 4-3 Changing Priority Values

$ mcr reg$cp REG> MODIFY VALUE HKEY_LOCAL_MACHINE\SYSTEM\REGISTRY\PRIORITY - _REG> /NAME=NODENAME3/DATA=20/TYPE=DWORD

In Example 4-3, the OpenVMS Registry server process on NODENAME1 goes into standby mode, and the OpenVMS Registry server process on NODENAME3 becomes active.

4.6 Connecting to the OpenVMS Registry from a Windows NT System

To connect to the OpenVMS Registry from a Windows NT system, you must do the following:

• On the OpenVMS system:
  • Install the Advanced Server for OpenVMS.
  • Configure the Advanced Server for OpenVMS.
• On the Windows NT system:
  • Install and configure any required hardware.
  • Install and configure the Windows NT Server or Workstation software.

When you access the OpenVMS Registry database from a Windows system, you will have all the privileges granted on your Windows NT system. For example, if you are logged in to the Windows NT system as an Administrator, you will be able to read and write to all keys and values in the OpenVMS Registry. Access to OpenVMS Registry keys is based on your Windows NT user profile (username and Group membership). Connect to the OpenVMS Registry through Advanced Server for OpenVMS; use the Windows Regedt32 application to view and change keys, values, and security settings.

A quota mechanism limits the size of the OpenVMS Registry database. The system assigns a quota to the root key datafile for every OpenVMS Registry file. By default, these root keys are the USERS key (REGISTRY$USERS.REG) and the LOCAL_MACHINE key (REGISTRY$LOCAL_MACHINE.REG).

The quota limits the size of the information in the file but does not include the size of information stored in other files, even if the files are part of the subtree.

The default quota and file-specific quotas are stored in the OpenVMS Registry under the HKEY_LOCAL_MACHINE\SYSTEM\Registry key.

4.8 OpenVMS Registry Security

A user can access (read and modify) the OpenVMS Registry directly in the following ways:

• From a Windows NT system (through a connection through Advanced Server for OpenVMS)
• Using the OpenVMS Registry system services ($REGISTRY[W])
• Using the OpenVMS Registry server management utility (REG$CP)

For a discussion of what system privileges and right identifiers each user needs, see the "OpenVMS Security Model" section of the OpenVMS Connectivity Developer Guide. For a description of how to grant the necessary system privileges and right identifiers, see the "Granting OpenVMS Registry Access Rights using the AUTHORIZE utility" section of the OpenVMS Connectivity Developer Guide.

You can change a key's security attributes only from a Windows NT system---you cannot change a key's security attributes from an OpenVMS system. OpenVMS does not create or manage Windows NT security attributes.

4.9 Backing Up and Restoring the OpenVMS Registry Database

The OpenVMS Registry includes a server management utility that allows you to back up and restore the entire OpenVMS Registry database to or from a file from the OpenVMS DCL prompt, as long as you have the required system privileges.

For more information about backing up and restoring the OpenVMS Registry database, see the "Backing Up and Restoring the OpenVMS Registry Database" section and the REG$CP server management utility CREATE SNAPSHOT command and the EXPORT command in the OpenVMS Connectivity Developer Guide. You can also use the OpenVMS Registry REG$CP online help facility to display information about the CREATE SNAPSHOT command and the EXPORT command.

4.10 Using the OpenVMS Registry in an Alpha Mixed-Version Cluster

The OpenVMS Registry Server can run in an Alpha mixed-version cluster. That is, the OpenVMS Registry can run in a cluster that includes OpenVMS versions other than OpenVMS Version 7.2-1; but the OpenVMS Registry server must be running on the node that is running OpenVMS Version 7.2-1.

4.11 Internationalization and Unicode Support

To integrate with Windows NT, the OpenVMS Registry is Unicode compliant. For more information about Unicode, see the OpenVMS Version 7.2 New Features Manual.

	privacy and legal statement
6614PRO_003.HTML