Document revision date: 19 July 1999
[Compaq] [Go to the documentation home page] [How to order documentation] [Help on this site] [How to contact us]
[OpenVMS documentation]

OpenVMS Connectivity Developer Guide
Previous Contents Index

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

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

8.5 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 SERVER REGISTRY_SERVER

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.

SET SERVER REGISTRY_SERVER

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.

8.6 OpenVMS Registry Failover in a Cluster

To increase the availability and reliability of the OpenVMS Registry, you can run multiple OpenVMS Registry servers in a cluster, up to one per node. No matter how many OpenVMS Registry servers you run, you have only one OpenVMS Registry database.

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.

8.6.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 8-1 shows priority values being assigned so that NODENAME1 will be the active OpenVMS Registry server process in the cluster.

Example 8-1 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 8-1, if NODENAME1 shuts down, control of the OpenVMS Registry database passes to the server process on NODENAME2.

Example 8-2 shows the system manager increasing the priority value of NODENAME3 to 20.

Example 8-2 Changing Priority Values 

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

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

8.7 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:

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

Caution
Be careful when you modify OpenVMS Registry database keys and values. If you damage the OpenVMS Registry database, you can affect all applications and users on the entire OpenVMS system or cluster.

8.8 OpenVMS Registry Quotas

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 contained within 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. For more information about these keys, see Section 7.3.

8.9 OpenVMS Registry Security

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

For a discussion of what system privileges and right identifiers each user needs, see Section 7.5.1. For a description of how to grant the necessary system privileges and right identifiers, see Section 7.5.1.1.

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.

8.10 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 Section 9.2 and the REG$CP server management utility CREATE SNAPSHOT command and the EXPORT command.

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

The OpenVMS Registry Server can run in an OpenVMS 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.

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

Chapter 9
OpenVMS Registry Server Management

9.1 Managing the OpenVMS Registry Server from the Command Line

The OpenVMS Registry includes a server management utility that allows you to update and display OpenVMS Registry information from the OpenVMS DCL prompt.

The utility also allows you to back up and restore the entire OpenVMS Registry database to or from a file, as long as you have the required system privileges. For more information about backing up and restoring the OpenVMS Registry database, see Section 9.2 and the CREATE SNAPSHOT, EXPORT, and IMPORT commands in the command reference section of this chapter.

To start the OpenVMS Registry server management utility, enter one of the following commands: 


$ RUN SYS$SYSTEM:REG$CP

or 


$ MCR REG$CP

Note
Before you can access the OpenVMS Registry database, the OpenVMS Registry server must be running either in the cluster or on the standalone system.

Table 9-1 lists and describes OpenVMS Registry server management utility commands.

Table 9-1 OpenVMS Registry Server Management Utility Commands
Command Identifier Action
CREATE DATABASE SYSPRV Creates a new OpenVMS Registry database file.
CREATE KEY REG$UPDATE Creates one or more keys in the OpenVMS Registry database.
CREATE SNAPSHOT SYSPRV Makes an immediate backup of the OpenVMS Registry database files.
CREATE VALUE REG$UPDATE Specifies the data component for a key.
DELETE KEY REG$UPDATE Removes one or more keys from the OpenVMS Registry database.
DELETE VALUE REG$UPDATE Removes one or more values from a specified key.
EXPORT REG$LOOKUP Exports the OpenVMS Registry to a text format.
IMPORT REG$UPDATE Imports a text-formatted version of a registry database to the OpenVMS Registry format.
LIST KEY REG$LOOKUP Displays all subkey information for a specified key.
LIST VALUE REG$LOOKUP Displays all values of a specified key.
MODIFY KEY REG$UPDATE Modifies the information of a specified key.
MODIFY VALUE REG$UPDATE Modifies the information of a specified value.
MODIFY TREE REG$UPDATE Modifies the information of a specified key and its subkeys.
SEARCH KEY REG$LOOKUP Displays the path name of all keys that match a specified key.
SEARCH VALUE REG$LOOKUP Displays the path name of all keys that match a specified value name.
SHOW COUNTERS REG$PERFORMANCE Displays counter information.
SHOW FILE REG$PERFORMANCE Displays OpenVMS Registry database file statistics.
SHOW INTERNAL REG$PERFORMANCE Displays internal values (used by shared libraries).
START MONITOR REG$PERFORMANCE Enables monitoring functions.
STOP MONITOR REG$PERFORMANCE Disables monitoring functions.
ZERO COUNTERS REG$PERFORMANCE Resets monitoring counters.

Note
A user who has the SYSPRV privilege can can execute all the commands listed in Table 9-1. You must specify an OpenVMS Registry identifier only if the user does not have SYSPRV privilege.

If you grant a user the REG$UPDATE identifier, in addition to the commands listed in Table 9-1, the user can also execute the following commands:

  • LIST KEY
  • LIST VALUE
  • SEARCH KEY
  • SEARCH VALUE

9.2 Backing Up and Restoring the OpenVMS Registry Database

The REG$CP server management utility includes two commands that allow you to back up and restore an OpenVMS Registry database.

9.2.1 Creating a Snapshot of the OpenVMS Registry Database

Use the following procedure to create a snapshot of the OpenVMS Registry database:

  1. Verify that the REGISTRY_SERVER process is running in the cluster.
  2. From an account with the SYSPRV privilege, enter the following commands: 


    $ MCR REG$CP
REG> CREATE SNAPSHOT

    The resulting snapshot consists of the following two files, located in the specified directory: 


     REGISTRY$LOCAL_MACHINE.RSS 
 REGISTRY$USERS.RSS

9.2.2 Restoring a Snapshot of the OpenVMS Registry Database

Use the following procedure to restore a snapshot of the OpenVMS Registry database:

  1. Shut down the REGISTRY_SERVER process on all nodes in the cluster. (For information about shutting down the OpenVMS Registry, see Section 8.4.)
  2. Verify that the OpenVMS Registry snapshot files are in the SYS$REGISTRY directory.
    If the OpenVMS Registry snapshot files are not in the SYS$REGISTRY directory, copy the OpenVMS Registry snapshot files to the SYS$REGISTRY directory.
  3. Rename the OpenVMS Registry snapshot files as follows: 


     $ RENAME REGISTRY$LOCAL_MACHINE.RSS REGISTRY$LOCAL_MACHINE.REG 
 $ RENAME REGISTRY$USERS.RSS REGISTRY$USERS.REG

  4. Restart the REGISTRY_SERVER process. (For information about starting the OpenVMS Registry manually, see Section 8.3.1.)

Caution
Any information that the system has written to the OpenVMS Registry database between the time of the last snapshot and this restore process will be lost.

9.3 OpenVMS Registry Server Management Utility Syntax

The following command section describes each OpenVMS Registry command in alphabetical order.

Note
In all the commands in this section, the key-name parameter is a string that specifies the full path of the key, beginning from one of following entry points:
  • HKEY_LOCAL_MACHINE
  • HKEY_USERS
  • HKEY_CLASSES_ROOT

You can also specify the strings REG$_HKEY_LOCAL_MACHINE, REG$_HKEY_USERS, and REG$_HKEY_CLASSES_ROOT.

For all server management commands, links are not followed. (For more information about links, see Section 7.2.1.3.)

To make key and values names case sensitive, enclose the keys and values in quotation marks (for example: "value").

CREATE DATABASE

Creates the basic OpenVMS Registry database files in the location specified by the SYS$REGISTRY logical. The command creates an empty database and loads the predefined keys.

If you enter this command and the database files already exist, the utility does not overwrite the existing files. The system displays a warning that the files already exist. If you want to create a new OpenVMS Registry database, you must first delete all previous versions of the database files. If you delete the OpenVMS Registry database files, you will lose all keys, subkeys, and values stored in the OpenVMS Registry.

This command requires the SYSPRV privilege.

The following table lists and describes the OpenVMS Registry database files.
File Description
REGISTRY$ROOT.DAT Root of the database
REGISTRY$USERS.REG HKEY_USERS tree
REGISTRY$LOCAL_MACHINE.REG HKEY_LOCAL_MACHINE tree
REGISTRY$MASTER.RLG The master commit log file
REGISTRY$REPLY.RLG Log file that tracks modification requests to the OpenVMS Registry database

Format

CREATE DATABASE

Parameters

None

Qualifiers

None

Examples


REG> CREATE DATABASE

Regenerates the basic OpenVMS Registry database files if the database files are lost or deleted.

CREATE KEY

Creates one or more keys in the OpenVMS Registry database.

This command requires the SYSPRV privilege or the REG$UPDATE rights identifier.

Format

CREATE KEY key-name [,...]

Parameters

key-name[,...]

Specifies the name of the key to create. You can create multiple keys by separating the keys with commas

Qualifiers

/WRITEBEHIND
/NOWRITEBEHIND (default)

Specifies that the key information must be written to disk immediately. /NOWRITEBEHIND specifies a write-through operation.

/VOLATILE=level
/NONVOLATILE (default)

Specifies whether or not the new key is volatile. If you are running the OpenVMS Registry on a standalone OpenVMS system, volatile keys are lost when the system reboots. If you are running the OpenVMS Registry in an OpenVMS cluster, volatile keys are lost when all notes in the cluster are rebooted.

The values for level are as follows:

/CACHE_ACTION=value

Specifies the cache attribute for the new key. The value can be WRITEBEHIND (default) or WRITETHRU (write to disk immediately).

/CLASS_NAME=string

Specifies the class name of the key.

/SECPOLICY=policy

Defines the security policy for the key. Currently the only valid policy is NT_40.

/LINK=(TYPE=value, NAME=key-name)

Defines the key as a link to another key. The link value must be one of the following:

To remove a link, enter the following: 


/LINK=(TYPE=NONE,NAME="")

Examples


REG> CREATE KEY/CACHE_ACTION=WRITEBEHIND HKEY_USERS\GUEST, HKEY_USERS\SYSTEM

Creates the GUEST and SYSTEM keys under the HKEY_USERS entry point. The keys are created with the write-behind attribute.

CREATE SNAPSHOT

Creates a snapshot of the OpenVMS Registry database. That is, the system writes all cached OpenVMS Registry keys or values and makes a copy of the OpenVMS Registry database files.

This command requires the SYSPRV privilege.

Format

CREATE SNAPSHOT

Parameters

None

Qualifiers

/DESTINATION=file-spec

Controls where the system will write the snapshot files. By default, the system creates the snapshot in the location specified by the SYS$REGISTRY logical.

If you specify the /DESTINATION qualifier but do not provide a valid directory, the system creates the snapshot files in the directory in which you started the OpenVMS Registry server.

/VERSIONS=number

Specifies how many previous versions of the snapshot files to keep.

Examples


REG> CREATE SNAPSHOT/DESTINATION=SYS$REGISTRY/VERSION=3

Creates a snapshot of the OpenVMS Registry database in the SYS$REGISTRY directory. If more than three versions of the OpenVMS Registry database snapshot files exist, the system deletes the oldest version (the same as purge/keep=3 command).

CREATE VALUE

Specifies the data component for the specified key. If the value does not exist, the command creates the value.

This command requires the SYSPRV privilege or the REG$UPDATE rights identifier.

Format

CREATE VALUE key-name

Parameters

key-name

Specifies the name of the key for which you will set the value.

Qualifiers

/FLAGS=flag

Specifies the data flags value. This is an application-dependent 64-bit flag specified as a decimal number or as a hexadecimal number preceded by 0x or %X.

/WRITEBEHIND
/NOWRITEBEHIND (default)

Specifies that the value must be written to disk immediately. /NOWRITEBEHIND specifies a write-through operation.

/DATA=value

The value can be one of the following:

/NAME=string

Specifies the name of the new value.

/TYPE_CODE=type

Specifies the type of the new value. The type value must be one of the following:

/LINK=(TYPE=value, NAME=key-name)

Defines the key as a link to another key. The link value must be one of the following:

To remove a link, enter the following: 


/LINK=(TYPE=NONE,NAME="")

Examples


REG> CREATE VALUE/DATA=COSMOS/TYPE=SZ/NAME=COMPUTERNAME HKEY_LOCAL_MACHINE\NODE

Creates the COMPUTERNAME value for the key HKEY_LOCAL_MACHINE\NODE and sets its type to SZ and its data value to COSMOS.

DELETE KEY

Removes a specified key from the OpenVMS Registry database. The system does not delete a key if the key has subkeys.

Caution
Deleting a key results in symbolic links not being followed. This is because the system deletes the key you specified, even if it has symbolic links.

Note
The OpenVMS Registry database predefined keys are reserved keys and cannot be deleted. These keys include HKEY_USER, HKEY_LOCAL_MACHINE, and HKEY_CLASSES_ROOT. For a complete list, see Section 7.3.

This command requires the SYSPRV privilege or the REG$UPDATE rights identifier.

Format

DELETE KEY key-path key-name

Parameters

key-path

Specifies the key path.

key-name

Specifies the name of the key to delete.

Qualifiers

/WRITEBEHIND
/NOWRITEBEHIND (default)

Specifies that the key information must be written to disk immediately. /NOWRITEBEHIND specifies a write-through operation.

Examples


REG> DELETE KEY HKEY_USERS\NODE GUEST

Deletes the GUEST key from the OpenVMS Registry database.

DELETE VALUE

Removes a value from a specified key.

Caution
Deleting a value results in symbolic links not being followed. This is because the system deletes the value you specified, even if it has symbolic links.

This command requires the SYSPRV privilege or the REG$UPDATE rights identifier.

Format

DELETE VALUE key-name value-name

Parameters

key-name

Specifies the key name whose value should be removed.

value-name

Specifies the value to remove.

Qualifiers

/WRITEBEHIND
/NOWRITEBEHIND (default)

Specifies that the information must be written to disk immediately. /NOWRITEBEHIND specifies a write-through operation.

Examples


REG> DELETE VALUE HKEY_USERS\GUEST PASSWORD

Deletes the PASSWORD value from the GUEST key.

EXPORT

Allows a user to export the OpenVMS Registry database content to a text format. You can export the entire database or specific keys and subkeys.

You can specify the exported file as a Windows NT compatible format or in an OpenVMS format. The IMPORT command support both Windows NT 4.0 Regedit format and the OpenVMS Registry format.

This command requires the REG$LOOKUP rights identifier. If you do not have the REG$LOOKUP rights identifier, you must have the SYSPRV privilege to export keys that require the REG$LOOKUP rights identifier.

Format

EXPORT [DATABASE | KEY [key-name [/[NO]SUBKEYS]]] [/LOG] [/OUTPUT=file-name ] [/FORMAT=[NT | OPENVMS]]

Parameters

DATABASE

Exports the full OpenVMS Registry database.

KEY [key-name [/[NO]SUBKEYS]]

Exports a specific OpenVMS Registry key and, optionally, its subkeys. NOSUBKEYS is the default.

Qualifiers

/LOG

Displays the export progress to the screen.

/OUTPUT=file-name

Specifies a name for the exported file. The default output file name is REGISTRY.TXT.

/FORMAT=[NT | OPENVMS]

Specifies the format in which the system writes the database. OPENVMS is the default.

Examples


REG> EXPORT DATABASE/LOG/OUTPUT=TUES_VERSION.TXT/FORMAT=NT

The EXPORT command in this example logs the progress of the export to the screen as the system exports the entire OpenVMS Registry database to the TUES_VERSION.TXT file in Windows NT 4.0 Regedit format.

IMPORT

Allows a user to import a text-formatted file (created by the EXPORT command) into an OpenVMS Registry database.

Also allows a user to import into an OpenVMS Registry database the Windows NT data exported by Windows NT 4.0 Regedit (from the Registry menu choose the Export Registry File... option).

Conversion of Windows NT binary values
You can import Windows NT binary values (such as configuration data) into the OpenVMS Registry database, even though OpenVMS does not support the binary values. The system displays a message when importing and converting unsupported binary values.

This command requires the REG$UPDATE rights identifier. If you do not have the REG$UPDATE rights identifier, you must have the SYSPRV privilege to import keys that require the REG$LOOKUP or REG$UPDATE rights identifier.

The following table summarizes how rights identifiers and privileges affect your ability to import and export keys.
If you have: You can export from Windows NT: You can import to the OpenVMS Registry:
No privileges.
No rights identifiers 		All keys created by Advanced Server for OpenVMS except HKEY_LOCAL_MACHINE\SECURITY Nothing
REG$LOOKUP All keys created by Advanced Server for OpenVMS Nothing
REG$UPDATE All keys created by Advanced Server for OpenVMS All keys created by Advanced Server for OpenVMS
SYSPRV All keys created by Advanced Server for OpenVMS All keys created by Advanced Server for OpenVMS

Format

IMPORT [/LOG] [/INPUT=file-name ]

Parameters

None

Qualifiers

/LOG

Displays the import progress to the screen.

/INPUT=file-name

Specifies a name of the file to import. The default input file name is REGISTRY.TXT.

Examples


REG> IMPORT/LOG/INPUT=TUES_VERSION.TXT

The IMPORT command in this example logs the progress of the import to the screen as the system imports the TUES_VERSION.TXT file.

LIST KEY

Displays the attributes for the specified key.

Note
Symbolic links are not followed.

This command requires the SYSPRV privilege or the REG$LOOKUP rights identifier.

Format

LIST KEY key-name

Parameters

key-name

Specifies the name of the key to list.

Qualifiers

/FULL

Displays all available information---that is, information displayed by the /LAST_WRITE, /CACHE_ACTION, /INFORMATION, /LINK_PATH, and /CLASS_NAME qualifiers.

/CACHE_ACTION=value

Specifies the cache attribute for the subkey. The value can be WRITEBEHIND (default) or WRITETHRU (write to disk immediately).

/CLASS_NAME

Displays the class name of the subkey.

/INFORMATION

Displays the information (subkey number, value number, subkey name max, and so on) about the specified key.

/LAST_WRITE

Displays the time when the subkey was last updated.

/LINK_PATH

Displays the key path to which the subkey is linked.

/OUTPUT=file-spec

Controls where the output of the command is sent. If you do not specify a file name, the system uses the default name REGISTRY.LIS.

Examples


REG> LIST KEY/FULL HKEY_USERS\GUEST 
 
Key name:            HKEY_USERS\GUEST 
Security policy:     REG$K_POLICY_NT_40 
Volatile:            REG$K_NONE 
Cache:               REG$K_WRITEBEHIND 
Class:               System Authorization 
Link Type:           REG$K_NONE 
Last written:         7-AUG-1998 12:42:08.55 
 
Key information: 
  Number of subkeys:             2        Number of values:              0 
  Max size of subkey name:      40        Max size of class name:       40 
  Max size of value name:        0        Max size of value data:        0 
 
Subkey(s): 
 
    Key name:            QUOTAS 
    Security policy:     REG$K_POLICY_NT_40 
    Volatile:            REG$K_NONE 
    Cache:               REG$K_WRITEBEHIND 
    Class:               Disk quota 
    Link Type:           REG$K_NONE 
    Last written:         7-AUG-1998 12:41:19.21 
 
    Key information: 
      Number of subkeys:             0        Number of values:              0 
      Max size of subkey name:       0        Max size of class name:        0 
      Max size of value name:        0        Max size of value data:        0 
 
    Key name:            IDENTIFIER 
    Security policy:     REG$K_POLICY_NT_40 
    Volatile:            REG$K_NONE 
    Cache:               REG$K_WRITETHRU 
    Class:               Disk quota 
    Link Type:           REG$K_SYMBOLICLINK 
    Link Path:           HKEY_LOCAL_MACHINE\SOFTWARE\IDENTIFIER\GUEST 
    Last written:         7-AUG-1998 12:42:08.55 
 
    Key information: 
      Number of subkeys:             0        Number of values:              0 
      Max size of subkey name:       0        Max size of class name:        0 
      Max size of value name:        0        Max size of value data:        0

The LIST KEY/FULL command in this example displays the GUEST key attributes as well as the name and attributes of the subkeys of GUEST.

Note
The Max sizes information shows the number of bytes, not characters. (Each character is 4 bytes long.)

LIST VALUE

Displays all values and value attributes of the specified key.

Note
Symbolic links are not followed.

This command requires the SYSPRV privilege or the REG$LOOKUP rights identifier.

Format

LIST VALUE key-name

Parameters

key-name

Specifies the name of the key to enumerate.

Qualifiers

/FULL

Displays all available information---that is, information displayed by the /TYPE_CODE, /LINK_PATH, /DATA_FLAGS, and /VALUE_DATA qualifiers.

/TYPE_CODE

Display the type code of the value.

/FLAGS

Displays an ASCII representation of the data flag of the value in hexadecimal format.

/LINK_PATH

Displays the key path to which the subkey is linked.

/DATA

Displays an ASCII representation of the value in hexadecimal format.

/OUTPUT=file-spec

Controls where the output of the command is sent. If you do not specify a file name, the system uses the default name REGISTRY.LIS.

Examples


REG> LIST VALUE/TYPE_CODE/DATA HKEY_LOCAL_MACHINE\SOFTWARE\FORTRAN 
 
   Key name:            HKEY_LOCAL_MACHINE\SOFTWARE\FORTRAN 
   Security policy:     REG$K_POLICY_NT_40 
   Volatile:            REG$K_NONE 
   Last written:        11-AUG-1998 16:27:55.81 
 
   Value(s): 
 
     Value name:   Version 
     Volatile:     REG$K_NONE 
     Type:         REG$K_SZ 
     Data:         5.3-50 
 
     Value name:   Date Installed 
     Volatile:     REG$K_NONE 
     Type:         REG$K_SZ 
     Data:         04-Jan-1998

The LIST VALUE/TYPE_CODE/DATA command in this example displays the FORTRAN key and its value names, types, and data.

MODIFY KEY

Modifies the attributes of the specified key.

Caution
Modifying a key results in symbolic links not being followed. This is because the system modifies the key you specified, not the key pointed to by the symbolic link.

This command requires the SYSPRV privilege or the REG$UPDATE rights identifier.

Format

MODIFY KEY key-name

Parameters

key-name

Specifies the name of the key to modify.

Qualifiers

/CACHE_ACTION=value

Specifies the cache attribute for the new key. The value can be WRITEBEHIND (default) or WRITETHRU (write to disk immediately).

/CLASS_NAME=string

Specifies the new class name of the key.

/WRITEBEHIND
/NOWRITEBEHIND (default)

Specifies that the key information must be written to disk immediately. /NOWRITEBEHIND specifies a write-through operation.

/NEW_NAME=new-key-name

Specifies the new name of the key.

/SECPOLICY=policy

Defines the security policy for the key. Currently the only valid policy is NT_40.

/LINK=(TYPE=value, NAME=key-name)

Defines the key as a link to another key. The link value must be one of the following:

To remove a link, enter the following: 


/LINK=(TYPE=NONE,NAME="")

Examples


REG> MODIFY KEY/CACHE_ACTION=WRITEBEHIND HKEY_USERS\GUEST

Modifies the cache attribute of the GUEST key.

MODIFY VALUE

Specifies the data component for the specified value. This command modifies an existing value.

Caution
Modifying a value results in symbolic links not being followed. This is because the system modifies the value you specified, not the value pointed to by the symbolic link.

This command requires the SYSPRV privilege or the REG$UPDATE rights identifier.

Format

MODIFY VALUE /NAME=string key-name

Parameters

key-name

Specifies the name of the key for which to set the value.

Qualifiers

/FLAGS=flag

Specifies the data flags value. This is an application-dependent 64-bit flag specified as a decimal number or as a hexadecimal number preceded by 0x or %X.

/WRITEBEHIND
/NOWRITEBEHIND (default)

Specifies that the value information must be written to disk immediately. /NOWRITEBEHIND specifies a write-through operation.

/DATA=value

Specifies the data for the value. The value can be:

/NAME=string

Specifies the name of the value.

/TYPE_CODE=type

Specifies the type of the new value. The type value must be one of the following:

/LINK=(TYPE=value, NAME=key-name)

Defines the key as a link to another key. The link value must be one of the following:

To remove a link, enter the following: 


/LINK=(TYPE=NONE,NAME="")

Examples


REG> MODIFY VALUE/DATA=COSMOS/TYPE=SZ/NAME=COMPUTERNAME HKEY_LOCAL_MACHINE\NODE

Creates COMPUTERNAME value for the key HKEY_LOCAL_MACHINE\NODE, and sets its type code to SZ and its data value to COSMOS.

MODIFY TREE

Modifies the information for the specified key and its subkeys.

Caution
Modifying a tree results in symbolic links not being followed. This is because the key and subkeys you specify are modified, not the key pointed to by the symbolic link.

This command requires the SYSPRV privilege or the REG$UPDATE rights identifier.

Format

MODIFY TREE key-name

Parameters

key-name

Specifies the name of key to modify.

Qualifiers

/CACHE_ACTION=value

Specifies the cache attribute for the key and its subkeys. The value can be WRITEBEHIND (default) or WRITETHRU (write to disk immediately).

/CLASS_NAME=string

Specifies the new class name for the given key and all its subkeys.

/WRITEBEHIND
/NOWRITEBEHIND (default)

Specifies that the key information must be written to disk immediately. /NOWRITEBEHIND specifies a write-through operation.

/SECPOLICY=policy

Defines the security policy for the key. Currently the only valid policy is NT_40.

Examples


REG> MODIFY TREE/CACHE_ACTION=WRITEBEHIND HKEY_USERS\GUEST

Modifies the cache attribute of the GUEST key and all its subkeys.

SEARCH KEY

Displays the path name of all the keys that match the specified key.

This command requires the SYSPRV privilege or the REG$LOOKUP rights identifier.

Format

SEARCH KEY key-search

Parameters

key-search

Specifies the key name for which to search.

Qualifiers

/OUTPUT=file-spec

Controls where the output of the command is sent. If you do not specify a file name, the system uses the default name REGISTRY.LIS.

Examples


REG> SEARCH KEY HKEY_LOCAL_MACHINE\...\NODE
HARDWARE\CLUSTER\NODE 
HARDWARE\LOCAL\NODE  
NODE

Displays all the key paths that match the HKEY_LOCAL_MACHINE\...\NODE selection. The ellipsis (...) wildcard specifies that there can be any number of subkeys between the HKEY_LOCAL_MACHINE entry point and the NODE subkey. Note that the search is not case sensitive.

SEARCH VALUE

Displays the path name of all the values that match the specified value name.

This command requires the SYSPRV privilege or the REG$LOOKUP rights identifier.

Format

SEARCH VALUE key-name value-name

Parameters

key-name

Specifies the name of the key path to search.

value-name

Specifies the value name for which to search.

Qualifiers

/OUTPUT=file-spec

Controls where the output of the command is sent. If you do not specify a file name, the system uses the default name REGISTRY.LIS.

Examples


REG> SEARCH VALUE HKEY_LOCAL_MACHINE\... *AM%
HARDWARE\CLUSTER\Name  
HARDWARE\CLUSTER\NODE\Name  
HARDWARE\LOCAL\NODE\Name  
NODE\COMPUTERNAME

Displays all the value names that match the HKEY_LOCAL_MACHINE\...\*am% selection. The ellipsis (...) wildcard specifies that there can be any number of subkeys between the HKEY_LOCAL_MACHINE entry point and the *am% value name. Note that the search is not case sensitive.

SHOW

Displays OpenVMS Registry server internal statistics and information.

This command requires the SYSPRV privilege or the REG$PERFORMANCE rights identifier.

Format

SHOW COUNTERS/FILE [name]

SHOW FILE [name]

Parameters

name

Identifies the file (used with the /FILE qualifier only).

Qualifiers

/FILE

Displays counters for the specified file or for all files.

/PERFORMANCE

Displays performance counters.

/OUTPUT=file-spec

Controls where the output of the command is sent. If you do not specify a file name, the system uses the default name REGISTRY.LIS.

Examples


REG> SHOW COUNTERS/FILE

Displays monitoring information from the OpenVMS Registry server.

START MONITORING

Starts a monitoring component within the OpenVMS Registry server.

This command requires the SYSPRV privilege or the REG$PERFORMANCE rights identifier.

Format

START MONITORING/FILE [name]

START MONITORING/PERFORMANCE

Parameters

name

Identifies the file (used with the /FILE qualifier only).

Qualifiers

/FILE

Start gathering counters for the specified file or for all files.

/PERFORMANCE

Start gathering performance counters.

Examples


REG> START MONITORING/PERFORMANCE

Enables a monitoring component of the OpenVMS Registry.

STOP

Stops a monitoring component within the OpenVMS Registry server.

This command is used to stop a monitoring component within the OpenVMS Registry server.

This command requires the SYSPRV privilege or the REG$PERFORMANCE rights identifier.

Format

STOP MONITORING/FILE [name]

STOP MONITORING/PERFORMANCE

Parameters

name

Identifies the file (used with the /FILE qualifier only).

Qualifiers

/FILE

Stop gathering counters for the specified file or for all files.

/PERFORMANCE

Stop gathering performance counters.

Examples


REG> STOP MONITORING/PERFORMANCE

Disables a monitoring component of the OpenVMS Registry.

ZERO COUNTERS

Initializes counters within the OpenVMS Registry server.

This command requires the SYSPRV privilege or the REG$PERFORMANCE rights identifier.

Format

ZERO COUNTERS/FILE [name]

ZERO COUNTERS/PERFORMANCE

Parameters

name

Identifies the file (used with the /FILE qualifier only).

Qualifiers

/FILE

Initializes the file counters for the specified file or for all files.

/PERFORMANCE

Initializes all performance counters.

Examples


REG> ZERO COUNTERS/PERFORMANCE

Resets the performance counters.

Previous Next Contents Index

  [Go to the documentation home page] [How to order documentation] [Help on this site] [How to contact us]  
  privacy and legal statement  
6539PRO_004.HTML