HP OpenVMS Systems Documentation
OpenVMS System Manager's Manual
D.3 Starting the OpenVMS Registry
You can control how the OpenVMS Registry will start as follows:
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:
Alternately, you can use the following command to start the OpenVMS Registry manually:
D.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:
D.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.
SHOW SERVER REGISTRY_SERVER
SET SERVER REGISTRY_SERVER
SET SERVER REGISTRY_SERVER
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.
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 D-1 shows priority values being assigned so that NODENAME1 will be the active OpenVMS Registry server process in the cluster.
In Example D-1, if NODENAME1 shuts down, control of the OpenVMS Registry database passes to the server process on NODENAME2 .
Example D-2 shows the system manager increasing the priority value of NODENAME3 to 20.
In Example D-2, the OpenVMS Registry server process on
goes into standby mode and the OpenVMS Registry server process on
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.
D.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
A user can access (read and modify) the OpenVMS Registry directly in the following ways:
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
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
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.
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.
An alphabetical list of terms used in the OpenVMS System Manager's Manual and their
access control list (ACL): A protection mechanism
using a more refined level of protection than that available with
UIC-based protection. ACLs can be used to grant or
deny access to individual users or groups of users.
access mode: Any of the four processor access modes in
which software executes. Processor access modes prevent system software
from inadvertently performing operations that might damage the system.
Processor access modes are in order from most to least privileged and
protected: kernel, executive, supervisor, and user. When the processor
is in any mode other than kernel mode, the processor is inhibited from
executing privileged instructions.
account: Each system user has an account. When you log
in, you log in under a particular account name and number. This number
informs the system where your files are and what kind of access to
other files and system facilities you should be given.
accounting files: Files where the system stores
information about resource use. Compare with current accounting
active set: In a multiprocessing system, the subset of
processors that have successfully run power-on diagnostics and are
actively participating in system operations. Compare with
active values: With system parameters, the set of
values that is stored in memory and is used by the active system. When
the system boots, it reads into memory the current
values stored in a parameter file on disk.
adjacent node: In a network, a node that is connected
to your node by a single physical line.
allocation class: In an OpenVMS Cluster environment,
for devices that are dual-ported between two computers, a numeric value
used to create a unique, path-independent device name.
answer file: A file in the form
SYS$UPDATE:product.ANS. The file is created when you install a
product initially, and you specify the Auto-Answer option. The file
contains a record of the answers you entered when you ran VMSINSTAL.COM
to install that product initially.
application service: A LAT service in
which LAN users can access only a specific program. Contrast with
general timesharing service.
area router: In a network, a node that performs
routing operations between areas and within its own area. Also called a
level 2 router. Compare with level 1
autoconfiguration: Autoconfiguration is the process of
discovering the hardware devices on a system and loading the
appropriate device drivers.
autostart feature: A feature that simplifies startup and ensures high availability of execution queues in an OpenVMS Cluster environment. It lets you perform the following actions:
autostart queue: An execution queue that takes
advantage of the autostart feature. When you create a
queue, you can designate it as an autostart queue.
available set: In a multiprocessing system, those
processors that have successfully completed the system's power-on
hardware diagnostics and may or may not be actively involved in the
system. Compare with active set.
backlink: In Files--11 disk structure, a pointer to
the directory in which a file resides.
banner page: A specially formatted page that prints at
the beginning and end of print jobs and files within print jobs. These
pages are helpful in identifying and separating output jobs, and the
files within those jobs, when they are printed.
base process priority: A base priority value that the
system uses to schedule a process. Priorities range from a low of 0 to
a high of 31; 0 through 15 are timesharing priorities and 16 through 31
are real-time priorities. Compare with job scheduling
batch execution queue: An execution queue that can
accept only batch jobs.
batch job: A detached process that sequentially runs
one or more command procedures. The user defines the list of command
procedures when submitting the job to a batch queue.
batch mode: An execution mode in which you can execute
a command procedure by submitting the procedure to a batch queue. When
resources are available, the system creates a detached process to
execute the commands in the procedure. Usually, processes running in
batch mode execute at a lower process priority, to avoid competing with
interactive users for system resources.
beginning-of-tape (BOT) marker: A piece of
photoreflective tape that delimits the beginning of the writable area
on a tape volume.
binding: On an InfoServer system, a function that
creates a virtual device unit on a local OpenVMS
block: On Files--11 disks, the basic unit by which
disk space is allocated (512 8-bit bytes). On magnetic tape, the size
of a block is determined by the user.
boot block: Virtual block 1 of the index file. The
boot (or bootstrap) block is almost always mapped to the logical block
0 of the volume. The book block contains the location and size of the
primary bootstrap image, which is used to boot the
system. Certain processors, in order to boot, must read the boot block
to obtain the location of the primary bootstrap image.
booting: Also called bootstrapping,
the process of loading system software from the system disk into
processor memory. You must install the operating system before you boot
the system for the first time. See also conversational
boot and nonstop boot.
bootstrapping: See booting.
bpi: Bits per inch; a measure used for characters of
data on tape. Also called density.
caching: A performance enhancement in which the system
stores information in memory; this includes information about a disk
volume's free space, file identifications, quota file entries, and file
capability: On VAX systems, software that makes the
services of the vector processor available to system users.
cathedral windows: Segmented windows created from
mapping windows; useful for reducing the overhead required to read
large files. The Buffered I/O Byte Count Limit (BITLM) limits the
number of cathedral windows a user can create.
circuit: In a network, a communications data path that
connects adjacent nodes. A circuit is not a physical
data path but, rather, a logical connection that operates over a
physical connection (a line). All input and output (I/O) between nodes
takes place over circuits.
cluster: On Files--11 media, a logical grouping of blocks; the basic unit by which disk space is allocated.
See also OpenVMS Cluster system.
CMIP: See Common Management Information
command procedure: A file containing DCL commands and,
optionally, data used by those commands. When you execute a command
procedure, the system reads the file and executes the commands it
contains. This eliminates the need for you to enter each command
separately. You can use command procedures to efficiently perform
routine tasks. A command procedure can also be executed in
command string: The complete specification of a
command, including the command name, command qualifiers, parameters,
and parameter qualifiers. Because a command can be continued on more
than one line, the term is used to define the entire command.
Common Management Information Protocol (CMIP): Draft
standard for network management operations on which DECnet-Plus network
management protocol is based. CMIP is used for encoding network
management operations that can be performed on an entity. CMIP permits
the exchange of information between a director and an agent. CMIP
supersedes the Phase IV Network Information and Control Exchange (NICE)
Compact Disc Read-Only Memory
(CD-ROM): Computer discs similar to the
CD-ROMs used for audio applications. The major
difference is that CD-ROM computer disc players have a
digital (rather than an audio) interface.
configuration database: In a network, each node has a
configuration database that includes information about the node and
other nodes with which it can communicate. The configuration database
is made up of a permanent database and
connection manager: In an OpenVMS Cluster environment,
the component that dynamically defines the OpenVMS Cluster system and
coordinates participation of computers in the cluster.
conversational boot: A booting operation in which you stop to perform special operations---for example, to change system parameter values---before booting. Contrast with nonstop boot.
Conversational boot operations are common in programming research and
development environments where you must alter operating conditions for
experimentation, testing, and debugging.
Coordinated Universal Time (UTC): International
standard for measuring time of day.
crash dump: When the operating system detects an
unrecoverable error or an inconsistency within itself that causes the
system to fail, it writes the contents of the error log buffers,
processor registers, and memory into the system dump
crash history file: A file storing information about
system crashes. Use the Crash Log Utility Extractor (CLUE) to display
the contents of the crash history file to understand and resolve the
issues responsible for crashes, and to obtain other useful data.
current accounting file: In an OpenVMS Cluster
environment, an accounting file for a particular node.
By default, the current accounting file is SYS$MANAGER:ACCOUNTNG.DAT.
current values: With system parameters, the set of
values that is stored in the default parameter file on disk and are
used to boot the system. When the system boots, it reads the current
parameter values into memory to create active values.
cylinder: On a disk, consists of all
tracks at the same radius on all recording surfaces of
data area: One of two divisions of
CD-ROM volume space; includes the remaining volume
space, beginning with logical sector 16.
data record storage: Within tape files, data records
are stored in variable-size data blocks. Each block contains one or
more records. RMS provides management of records.
DECevent: On Alpha systems, the event management
utility that provides an interface between a system user and the
operating system's event log files.
DECnet: Generic name for the software and hardware
products that allow various Compaq operating systems to participate in
a network. DECnet allows a system to function as a node in a network.
See also DECnet Phase IV, DECnet-Plus for
OpenVMS, and Compaq TCP/IP Services for
DECnet Phase IV: Older version of DECnet; available
for separate installation as a layered product.
DECnet-Plus for OpenVMS: The version of DECnet that is
available with the installation procedure for the OpenVMS operating
system. DECnet-Plus is Compaq's implementation of the Digital Network
Architecture (DNA) Phase V.
default values: With system parameters, the set of
values provided on your distribution kit and stored in the default
list. These values allow you to boot any supported configuration.
density: A measurement, in bits per inch, used for
characters of data on tape.
device: Hardware that allows access to storage media;
also called drive.
device control library: A text library that contains
user-written modules consisting of text or escape sequences. See also
device control module.
device control library module: A user-written module in a device control library. Device control library modules can be used for the following purposes:
See also page setup module, reset
module, and setup module.
device driver: A system component that controls I/O
operations for a particular device type. For a device to function on a
system, the device must be connected and the device driver must be
loaded into memory.
Compaq TCP/IP Services for OpenVMS: Compaq
implementation of the TCP/IP protocol suite and Internet services for
OpenVMS Alpha and VAX operating systems.)
disk: Physical media on which files reside.
disk quota: A method for maintaining and enforcing
limits on the amount of disk space available to users on a public
volume. See also quota file.
drive: Hardware that allows access to storage media;
also called device.
end node: In a network, a node that does not perform
end-of-tape (EOT) marker: A piece of photoreflective
tape that delimits the end of the writable area on a tape volume.
ERRFMT process: System process that periodically
empties the error log buffers, transforms the descriptions of the
errors into standard formats, and stores the formatted information in
the error log file on the system disk.
error log dump file: On Alpha systems, file to which
the contents of error log buffers are written (in addition to the
system dump file). The error log dump file is provided so that the
system can be updated on reboot to include error log entries that were
created but not written at the time of a system crash.
error log file: The operating system automatically
records device and CPU error messages in this file. The Error Log
utility invokes the Error Log Report Formatter (ERF)
to selectively report the contents of an error log file.
Error Log Report Formatter (ERF): A system component
invoked by the Error Log utility to selectively report the contents of
the error log file.
Ethernet: A single shared network channel, with all
nodes having equal access to the channel. Ethernet offers local and
remote connections as one integral network.
event classes: Categories of security-relevant events.
The system always audits several event classes.
executable image: An image that can be run in a
process. It is linked with the /EXECUTABLE qualifier (or without the
/SHAREABLE qualifier) of the Linker utility.
execution queue: A queue that accepts batch or print
jobs for processing. Compare with generic queue.
executive: A set of programs in the operating system
that controls the running of routines that perform I/O, resource
allocation, and program execution. See also executive
executive mode: The second most privileged processor
access mode. OpenVMS Record Management Services (RMS)
and many system service procedures execute in executive mode.