Document revision date: 15 July 2002

The OpenVMS Registry server is installed as part of the OpenVMS system installation.

Before you can use the OpenVMS Registry, you must configure the OpenVMS Registry server. For more information about configuring the OpenVMS Registry server, see Section 13.2.

The first time you start the OpenVMS Registry server using the startup process described in Section 13.3, the OpenVMS system creates the OpenVMS Registry database.

You can access the OpenVMS Registry in several ways. Depending on how you want to access the OpenVMS Registry, you must install the following products:

• If you want to access the OpenVMS Registry using the COM APIs, you must install COM for OpenVMS and populate the OpenVMS Registry database. For more information about installing COM for OpenVMS, see Chapter 4. For more information about populating the OpenVMS Registry database, see Section 6.2.
• If you want to access the OpenVMS Registry using the Windows NT application RegEdt32 , you must first install, configure, and start Compaq Advanced Server for OpenVMS. For more information, see the Compaq Advanced Server for OpenVMS documentation.

You can also access the OpenVMS Registry using the OpenVMS Registry server management utility or the OpenVMS Registry system services, which are installed as part of the OpenVMS Registry.

13.2 Configuring the OpenVMS Registry with REG$CONFIG

The OpenVMS Registry configuration procedure (REG$CONFIG) provides information about the OpenVMS Registry server status and the OpenVMS Registry database location, and allows you to change OpenVMS Registry logical names and paths.

Enter the following command to invoke the OpenVMS Registry configuration procedure:

$ @SYS$MANAGER:REG$CONFIG

The system displays the following menu:

--------------------------------------------------------- OpenVMS Registry Configuration Utility ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 - Configure OpenVMS Registry logical names and directory paths 2 - Display OpenVMS Registry logical names and directory paths 3 - Check the state of the OpenVMS Registry server 4 - Start the OpenVMS Registry server on this node 5 - Convert to latest database version and/or reclaim database H - Help about this utility [E] - Exit Please enter your choice : ---------------------------------------------------------

To select an option, enter the option number. The options are as follows:

• 1 - Configure OpenVMS Registry logical names and directory paths
  Allows you to configure the OpenVMS Registry server startup value and specify the location of the OpenVMS Registry database.
  For this procedure, see Section 13.2.1.
• 2 - Display OpenVMS Registry logical names and directory paths
  Displays the current values of the OpenVMS Registry server logical (startup value) for this node and the OpenVMS Registry database location.
• 3 - Check the state of the OpenVMS Registry server
  Displays the current state of the OpenVMS Registry server. The system displays one of the following:

  The OpenVMS Registry server is started in the cluster. The OpenVMS Registry server is started on this node. The OpenVMS Registry server is not started.

• 4 - Start the OpenVMS Registry server on this node
  Starts the OpenVMS Registry server on the current node. The system displays the following message:

  The OpenVMS Registry server has successfully started.

• 5 - Convert to latest database version and/or reclaim database
  This option can be used to convert an existing database to the latest version. The latest version is determined by the currently running server.
  This option can also be used to compact the database. Over time, the database can become fragmented in much the same way that a disk can become fragmented. Compacting the database makes it more efficient and requires less disk space.
• H - Help about this utility
  Displays online help for OpenVMS Registry Configuration utility options.
• [E] - Exit
  Exits the OpenVMS Registry Configuration utility.

The system displays the following questions:

1. The system prompts you to enter standalone or cluster information. The system displays the following message:

   Is this system now a node in a cluster or will this system become part of a cluster? (Y/N/Q):

2. The system displays the current information about the REG$TO_BE_STARTED logical, then prompts you to change the value.

   - REG$TO_BE_STARTED - [current value of REG$TO_BE_STARTED] NOTE: Setting this logical to TRUE starts the OpenVMS Registry server automatically when the system boots. Setting this logical to FALSE prevents the OpenVMS Registry server from starting when the system boots and prevents other products from starting the OpenVMS Registry server. If the OpenVMS Registry Server is not started at boot time, but other products that require an OpenVMS Registry server are able to start the OpenVMS Registry server, you do not need to assign a value to this logical. Do you want to change this value? (Y/N/Q) [Y]:

   
   If you choose Y , the system prompts you for the new value.

   Enter the new value (TRUE/FALSE/NOVAL/Q):

   
   Enter one of the following:

   Action	Value
   Start the OpenVMS Registry server on reboot. Allow other products to start the server.	TRUE
   Do not start the OpenVMS Registry server on reboot. Do not allow other products to start the server.	FALSE
   Do not start the OpenVMS Registry server on reboot. Allow other products to start the server. (Deassigns the logical name.)	NOVAL
   Quit this procedure and return to the OpenVMS Registry Configuration utility menu.	Q

   In which logical name table do you want the logical defined? (SYSTEM/SYSCLUSTER/Q) :

   
   Enter one of the following:

   Action	Value
   Add the REG$TO_BE_STARTED logical to the LNM$SYSTEM logical name table. This table contains names that are shared by all processes in the system.	SYSTEM
   Add the REG$TO_BE_STARTED logical to the LNM$SYSCLUSTER logical name table. This table contains names that are shared by all processes in an OpenVMS Cluster.	SYSCLUSTER
   Quit this procedure and return to the OpenVMS Registry Configuration utility menu.	Q

   
   After you enter the new or updated value, the system confirms the change and displays the line you must add to your SYLOGICALS.COM file.

   The logical REG$TO_BE_STARTED has been temporarily defined. Before you reboot the system you must edit your SYLOGICALS.COM to include the line: DEFINE/TABLE=table-name REG$TO_BE_STARTED value Press [Enter] to continue.

3. The system displays the current information about the SYS$REGISTRY logical, then prompts you to change the value.

   - SYS$REGISTRY logical - current value of SYS$REGISTRY Note: When the OpenVMS Registry server is started, the system creates an OpenVMS Registry database at this location. If an OpenVMS Registry database already exists on your system, you must redefine the SYS$REGISTRY logical to point to the existing OpenVMS Registry database location. Do you wish to change this value? (Y/N/Q) [Y]:

   
   If you choose Y , the system prompts you for the new value.

   Enter the new value for SYS$REGISTRY ("yourvalue"/NOVAL/Q):

   
   Enter one of the following:

   Action	Value
   Define a new or changed location for the OpenVMS Registry database.	A valid directory specification, such as DKA0: [SYS$REGISTRY].
   Deassign the logical name.	NOVAL
   Quit this procedure and return to the OpenVMS Registry Configuration utility menu.	Q

4. The system displays your updated value and prompts you to confirm the value.

   You have entered: value Is this correct? (Y/N/Q) [Y]:

5. The system prompts you to enter a logical table name in which to store the new or updated logical.

   In which logical name table do you want the logical defined? (SYSTEM/SYSCLUSTER/Q):

   
   Enter one of the following:

   Action	Value
   Add the SYS$REGISTRY logical to the LNM$SYSTEM logical name table. This table contains names that are shared by all processes in the system.	SYSTEM
   Add the SYS$REGISTRY logical to the LNM$SYSCLUSTER logical name table. This table contains names that are shared by all processes in an OpenVMS Cluster.	SYSCLUSTER
   Quit this procedure and return to the OpenVMS Registry Configuration utility menu.	Q

   
   After you enter the new or updated value, the system confirms the change and displays the line you must add to your SYLOGICALS.COM file.

   The logical SYS$REGISTRY has been temporarily defined. Before you reboot the system you must edit your SYLOGICALS.COM file to include the line: DEFINE/TABLE=table-name SYS$REGISTRY dir-spec Press [Enter] to continue.

6. The system displays information about the location of the OpenVMS Registry database.

   - SYS$REGISTRY directory - [directory status]

   
   If the directory does not exist, the system prompts you to create the directory.

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

Beginning with OpenVMS Version 7.3-1, the OpenVMS Registry supports two database formats, Version 1 and Version 2. The Version 2 database format includes an index access that improves on the access performance provided in the Version 1 database format.

The Registry server supports both database formats. To take advantage of the indexing feature, you must convert a Version 1 database to the Version 2 format.

Who Should Convert

Converting the Registry database is optional. Large databases are more likely to benefit from converting to Version 2. The more subkeys or values on a key, the more likely it is that there will be a performance improvement from using the Version 2 database. For databases where there are only one or two subkeys or values on most keys, converting to Version 2 will yield minimal performance improvement.

Who Should Not Convert

Do not convert the Registry database to Version 2 if you plan to run Registry servers on nodes in a mixed-version cluster. Registry servers on nodes running versions of OpenVMS prior to Version 7.3-1 cannot access a Version 2 database. Operating in this manner is not supported.

13.2.2.1 Converting an Existing Database

To convert an existing database to Version 2, invoke REG$CONFIG and select step 5, "Convert to latest database version and/or reclaim database," and follow the instructions. Be sure to invoke REG$CONFIG on a node that normally runs the Registry server. You cannot run REG$CONFIG on a node that explicitly disables the Registry server, that is, a node on which the REG$TO_BE_STARTED logical is FALSE.

The command procedure saves a copy of the current database in a separate directory, both in binary and EXPORT command (ASCII text) format.

The procedure requires an interruption in Registry services, so execute it at a time when this will cause minimal disruption. Prior to shutting down the Registry server, you must also shut down all layered products that use the Registry: COM for OpenVMS, Advanced Server for OpenVMS, and any other third-party applications.

Be sure to shut down these applications on all nodes in the cluster.

The command procedure informs you when to shut down these services and pauses while you perform this task. You should shut down in this order:

1. Shut down any third-party applications that use Registry.
2. Shut down COM for OpenVMS using SYS$STARTUP:DCOM$SHUTDOWN.COM.
3. Shut down Advanced Server for OpenVMS using SYS$STARTUP:PWRK$SHUTDOWN.COM.
4. Shut down the Registry server on all nodes in the cluster.

There are several ways to determine the version of a given Registry database.

• For a database currently in use, enter the command:

  $ MCR REG$CP LIST VALUE HKEY_LOCAL_MACHINE\SYSTEM\REGISTRY

  
  The value Database Version contains the version of the database currently loaded. Database versions prior to Version 2 do not have a Database Version value.

• For an exported database, look for the following statement in the exported database file:

  Database Version"=dword:00000002"

  
  Exported databases prior to Version 2 do not contain this statement.

• The files SYS$MANAGER:REGISTRY$SERVER.LOG and .ERR identify the version of the database opened by the Registry server when it starts up.
• For a given set of registry files, dump the REGISTRY$ROOT.DAT file. The second longword indicates the database version.

You can also use Step 5 in REG$CONFIG to reclaim the database, which reclaims wasted space that can occur over time as the database becomes fragmented. Follow the same instructions as for converting the database. You can repeat this procedure as often as you like.

REG$CONFIG does not allow you to reclaim a Version 1 database. However, you can manually reclaim a Version 1 database by performing the steps in the following section.

13.2.2.4 Manual Conversion and Reclamation

Conversion and reclamation of a database use the Registry Import/Export feature. The current Registry database is exported, a new database is created, then the original database is imported. You can perform these steps manually as follows:

1. Shut down all applications in the cluster that use Registry (described in Section 13.2.2.1), including COM for OpenVMS and Advanced Server.
2. Enter the following command:

   $ MCR REG$CP EXPORT DATABASE/OUTPUT=(filespec)

   
   If you do not specify a value for /OUTPUT, it defaults to REGISTRY.TXT in your current default directory.

3. Shut down the Registry server on all nodes in the cluster using the following command:

   $ SET SERVER REGISTRY/CLUSTER/EXIT

4. Preserve the current database by copying all of the files in SYS$REGISTRY to a separate directory.
5. Delete all the files in SYS$REGISTRY with the exception of REGISTRY$CONFIGDONE.DAT.
6. Start the Registry server on one node in the cluster using the following command:

   $ SET SERVER REGISTRY/START [/NODE=node]

7. Create a new Registry database using the following command:

   $ MCR REG$CP CREATE DATABASE

   Note The new database will default to a Version 2 database. To reclaim without converting to Version 2, enter the following command: $ MCR REG$CP CREATE DATABASE/VERSION=1

8. Import the original database using the following command:

   $ MCR REG$CP IMPORT/INPUT=(filespec-from-step-2)

   
   If you do not specify a value for /INPUT, it defaults to REGISTRY.TXT in your current default directory.

9. Start the Registry server on any remaining nodes on which you want it to run (see Step 6).
10. Restart any applications that were stopped in Step 1.

You can control how the OpenVMS Registry will start 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 13.2 to control how the OpenVMS Registry starts.

13.3.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. The following command procedure ensures that the server process quotas are set to the required minimum values:

$ @SYS$STARTUP:REG$STARTUP.COM

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

$ SET SERVER REGISTRY_SERVER/START

13.4 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

	privacy and legal statement
6539PRO_012.HTML