Updated: 11 December 1998 |
OpenVMS System Manager's Manual
Previous | Contents | Index |
Local Area VAXcluster configuration: A VAXcluster
configuration in which a single VAX computer serves as the management
center of the cluster, plus one or more VAX computers that are
connected to this hub.
local cluster: In the System Management utility
(SYSMAN), the node from which you are executing SYSMAN.
local node: In a network, the node on which you are working.
In the System Management utility (SYSMAN), the node on which you execute SYSMAN.
Contrast with remote node.
logical block: Organizational unit of volume space.
The logical block size cannot exceed the logical sector size.
logical block numbering: Begins with the first byte in
the volume space and continues in a sequentially ascending order
through the remainder of the volume space.
logical link: In a network, connects two processes and
carries a stream of two-way communications traffic between the
processes over a circuit. A single circuit established
between two nodes can support many logical links concurrently.
logical name table: A table containing definitions of
systemwide logical names that can be used by any process in the system.
logical queue: A special type of generic output queue
that transfers print jobs to another output execution queue. You might
use this kind of queue to temporarily redirect a queue when the device
on which it runs is broken.
logical sector: Organizational unit of a volume; consists of one or more physical sectors. No more than one logical sector can begin in any physical sector.
Logical sectors are numbered in ascending order, with 0 assigned to the
logical sector having the lowest physical address containing recorded
data. Each logical sector includes a data field made up of 2048 or more
bytes (the number of bytes always equals a power of 2).
login command procedure: A command procedure that
executes each time a user logs in. Add commands to a login command
procedure to execute commands when a user logs in, for example, to set
up the user environment.
login (LGI) system parameters: System parameters that
control login functions. The names of these system parameters begin
with LGI.
loopback tests: In a network, a series of tests to
help determine whether the network is operating properly.
lost file: A file that is not linked to a directory.
When you delete a directory file (a file with the file type .DIR)
without first deleting its subordinate files, the files referred to by
that directory become lost files. Lost files are a nonproductive use of
disk space and act as debits against a user's disk
quota.
Magnetic Tape Ancillary Control Process (MTACP): The
internal software process of the operating system that interprets the
logical format of standard labeled tape volumes.
maintenance release: A release of the operating system
that is applied with an update procedure.
managers: Devices on the network through which
management is done using the Extensible Simple Network Management
Protocol (eSNMP). Managers exchange information with master
agents or subagents, which are devices such as routers and
servers on the network being managed.
mandatory update: A software update that is required
immediately after upgrading or installing the operating system.
mass storage control protocol (MSCP) server: In an
OpenVMS Cluster environment, the component that implements the MSCP
protocol, which is used to communicate with a controller for DSA disks,
such as RA-series disks. In conjunction with one or both of the disk
class device drivers (DUDRIVER, DSDRIVER), the MSCP
server implements this protocol on a computer, allowing the computer to
function as a storage controller.
master agents: Devices such as routers and servers on
the network being managed (using the Extensible Simple Network
Management Protocol (eSNMP)). Master agents or subagents exchange
information with managers, which are the devices on
the network through which the management is done.
master file directory (MFD): The file that contains
the name of all user file directories on a disk.
media: The physical substance on which you can store
data.
mount verification: A recovery mechanism for disk and
tape operations. If a device goes off line or is
write-locked while mount verification is enabled, you
can correct the problem and continue the operation.
multivolume file: A file that is continued on another
volume when the data blocks of a file or related files do not
physically fit on one volume (a reel of magnetic tape).
network: A means of connecting computers that allows
them to share or transfer information or communications. A network
includes two or more computers that are connected, and the hardware and
software that makes those connections.
network proxy account: A user account that allows
users on a remote node in a network to access data by
way of a local account on your system. Proxy accounts are useful when
you want to grant one or more users on a remote node access to specific
files but you do not want to give them a private account on your system.
new domain part (IDP): Unique network identifier that
allows users on a DECnet-Plus network to communicate with users on
other OSI networks, either through electronic mail, EDI, FTAM, VTP, or
other internetwork utilities.
node: In a network, a computer system that is
connected to another system in a network---by means of cables,
telephone lines, microwave and satellite links, for example.
nonlocal cluster: In the System Management utility
(SYSMAN), any cluster other than the one from which you are executing
SYSMAN.
nonlocal environment: In the System Management utility
(SYSMAN), your environment when you are not working on your local node
or within your own cluster.
nonstop boot: The most common booting operation. You
perform a nonstop boot if you do not want to stop to perform special
operations---for example, to change system parameter values---before
booting. Contrast with conversational boot.
object: In a network, a process to which a logical link connects. Some objects are DECnet programs---for example, the Mail object; other objects are user-written programs.
For two programs to communicate over the network, the source program on
the local node establishes a logical link with the
object on the remote node.
OPCOM messages: Messages broadcast by the Operator
Communication Manager (OPCOM). These messages are displayed on
operator terminals and written to the operator
log file. The messages might be general messages that you
send, user requests, operator replies, or system events.
OPCOM process: The system process that manages
Operator Communication Manager (OPCOM) operations.
OpenVMS Cluster system: A loosely coupled configuration of two or more computers and storage subsystems, including at least one Alpha computer. An OpenVMS Cluster system appears as a single system to the user, even though it shares some or all of the system resources. When a group of computers shares resources in an OpenVMS Cluster environment, the storage and computing resources of all the computers are combined, which can increase the processing power.
See also VAXcluster system.
operator log file: The Operator Communication Manager
(OPCOM) records messages in this file. The file is named
SYS$MANAGER:OPERATOR.LOG.
operator terminals: Terminals designated to display
messages broadcast by the Operator Communication Manager (OPCOM).
Usually, the console terminal (with the device name OPA0:) is the
operator terminal. However, you can designate any user terminal as an
operator terminal.
output execution queue: A queue that accepts jobs for
processing by a symbiont. The queue
manager sends the symbiont a list of files, which the user
defines when submitting the job. An output symbiont transfers data from
a disk to an output device. As the symbiont processes each file, it
produces output for the device it controls, such as a printer or a
terminal.
owner UIC: Used with UIC-based
protection, usually the UIC of the person who created a file
or volume.
page: A unit used for allocating and deallocating memory.
On VAX systems, a page is 512 bytes.
On Alpha systems, a page can be 8 kilobytes (KB) (8192 bytes), 16KB,
32KB, or 64KB. The initial set of Alpha computers uses a page size of
8192 bytes. Compare with pagelet.
page file: In a paging operation, the
file to which the system writes paged portions of memory. Your
distribution kit includes a page file named SYS$SYSTEM:PAGEFILE.SYS. If
necessary, SYS$SYSTEM:PAGEFILE.SYS can be used in place of the system
crash dump file.
pagelet: On Alpha systems, a unit of memory in a
512-byte quantity. One Alpha pagelet is the same size as one VAX page.
Also, on an Alpha 8KB computer, 16 Alpha pagelets equal 1 Alpha page.
page setup module: A device control
module inserted at the beginning of each page of a print job.
paging: A memory management operation to efficiently
use the physical memory allotted to a process by moving information
between physical memory and files stored on disk. In paging, the system
moves infrequently used portions of a process workspace out of physical
memory to a file. Compare with swapping.
PAK: See Product Authorization Key
(PAK).
partition: A logical subset of a read/write disk. A
single disk can be subdivided into several partitions, each of which of
which can be used independently. The partitions appear to be whole
disks.
permanent database: In a network, a permanent copy of
the DECnet configuration database. When you start the
network, the permanent database provides the initial values for the
volatile database. Changes remain after the network is
shut down, but do not affect the current system.
permanently open image: A known image
where directory information on the image file remains permanently
resident in memory, eliminating the usual directory search required to
locate a file.
physical dump: A crash dump
containing the entire contents of physical memory to the system
dump file. Compare with selective dump.
physical operation: In the Backup utility, an
operation that copies, saves, restores, or compares an entire volume by
logical blocks, ignoring any file structure.
physical sector: Division of a system or data area;
smallest addressable unit on an ISO 9660 CD-ROM.
primary bootstrap image: Program that the boot block points to, which allows access to the system disk by finding the the secondary bootstrap image, SYSBOOT.EXE, and loading it into memory.
On VAX systems, the primary bootstrap image is VMB.EXE.
On Alpha systems, the primary bootstrap image is APB.EXE.
primary page and swap files: The default page
file and swap file provided with your
distribution kit. These files are named SYS$SYSTEM:PAGEFILE.SYS and
SYS$SYSTEM:SWAPFILE.SYS. Contrast with secondary page and swap
files.
primary processor: In a multiprocessing system, the
processor that is either logically or physically attached to the
console device and is the target of the console commands that bootstrap
the multiprocessing system. The primary processor is responsible for
starting other processors in the multiprocessing system. It also serves
as the system timekeeper.
print forms: You can use print forms with output queues to determine certain page formatting attributes (such as margins and page length). In addition, the paper stock specified in a form determines whether a job is printed; if the stock of a job's form does not match the stock of the form mounted on the queue, the job is not printed.
Compaq supplies a default print form named DEFAULT. You can create
additional forms if users need help formatting output, or if certain
print jobs require special paper.
print job: An entry in an output queue that specifies
a file or files to be printed on a printer. The user defines the file
or files to be printed when submitting the job. When a printer is
available, the queue manager sends the file to a
symbiont for formatting and printing.
printer queue: A type of output execution queue that
uses a symbiont to direct output to a printer. Compare
with server queue and terminal queue.
priority: See base process priority
or job scheduling priority.
private volume: A file-structured disk volume that
contains only private files.
privileged image: A known image where
increased privileges are temporarily assigned to any
process running the image, permitting the process to exceed its user
authorization file (UAF) privilege restrictions during execution of the
image. In this way, users with normal privileges can run programs that
require higher-than-normal privileges.
privileges: A means of restricting the functions users
are authorized to perform on the system. System managers require
privileges that are denied to most users.
process limits and quotas: User authorization file
(UAF) parameters you can set for a user account to control the usage of
system resources by processes in that account. (UAF parameters are
different than system parameters.) You set values for process limits
and quotas using the Authorize utility.
Product Authorization Key (PAK): Information,
typically on a piece of paper, provided for many Compaq products. The
data provided in the PAK allows you to register a software
license in the license database on a system.
product configuration file (PCF): Optional POLYCENTER
Software Installation utility file that might be supplied by the
software manufacturer, or you can create it. A PCF contains responses
to some or all of the installation questions for a product. It can
provide default or required choices, which might differ from the
default choices provided in the PDF.
product database (PDB): Database that is created
automatically by the POLYCENTER Software Installation utility. When
products are installed, the files and other objects that make up the
product, such as directories and accounts, are recorded in the PDB. The
configuration choices made during installation are also recorded.
product description file (PDF): File provided by the
software manufacturer containing all the information the POLYCENTER
Software Installation utility needs for installing either a software
product or a set of software products.
product text file (PTF): POLYCENTER Software
Installation utility file that is optionally supplied by the software
manufacturer. It provides information about the product including
product name, producer, configuration choice descriptions, and message
text used during product installation.
protected image: A known image that
is a shareable image and contains protected code.
Protected code is code that runs in kernel mode or
executive mode but that can be called by a
user mode image.
protection code: Used with UIC-based
protection, indicates who is allowed access and for what
purposes.
public volume: A Files--11 volume that any user on the
system can access and that can contain both private and public files.
queue: Allows users to submit requests for printing or
batch processing. The system prints users' print jobs or processes
users' batch jobs as resources allow.
queue characteristics: Characteristics you can define
and assign to a queue to control the batch or print jobs that execute
on the queue.
queue database: A file or files that store information
about queues and batch and print jobs.
queue manager: The system component that controls
queue activity.
quota file: On Files--11 volumes, the file that
records all users who are allowed to use a disk and that shows their
current disk usage and their maximum disk allocation. A quota file,
QUOTA.SYS, which is stored in directory [000000] with other system
files, requires 1 block of disk storage for every 16 entries. See also
disk quotas.
reconfiguration: After installation of a product,
changing the configuration choices made during the installation.
record blocking: On Files--11 volumes, the grouping of
individual records into a block, thereby reducing wasted space.
remote node: In a network, a node that is accessible to the node you are working on (the local node) over the network.
In the System Management utility (SYSMAN), any node other than the one on which you are executing SYSMAN.
Contrast with local node.
reset module: A device control module
inserted at the end of each print job. Use reset modules to reset a
printer at the end of a job.
resident image: On Alpha systems, a known
image that improves the performance of a shareable
image. With a resident image, portions of images that contain
code are moved into system space, where they reside on a large single
page, thus improving performance.
root volume: The first volume in a volume
set. Each volume in the volume set is identified by a volume
number relative to the root volume, which is always relative to volume
1.
router: In a network, a node that performs routing
operations.
routing: In a network of more than two nodes, the process of directing a data message from a source node to a destination node (known as an end node). Both routers and end nodes can send messages to and receive messages from other nodes in the network.
In a TCP/IP network. routing is the process of directing a data message
from a source host to a destination host. See also
host.
ruleset: Software routine or function that is
analogous to an executable file; used by DECevent.
save set: A special file used by the Backup utility.
The Backup utility saves files to a save set and restores files from a
save set. Installation and upgrade procedures restore product files
from a save set to your system disk.
scalar: A single data item, having one value. Compare
with vector.
secondary bootstrap image: Image that allows access to
the system disk: SYS$SYSTEM:SYSBOOT.EXE.
secondary page and swap files: Additional page
files and swap files that you might create
for performance or disk space reasons. The system uses the space in the
secondary files for paging and swapping in addition to the space in the
primary page and swap files.
secondary processor: In a multiprocessing system, any
processor that is not a primary processor.
sector: The smallest unit discernible to the Files-11 On-Disk structure. For most Files-11 disks, a sector is equivalent to a block (512 bytes).
On ISO 9660 volumes, a uniquely addressable unit; each sector on a
CD-ROM comprises a sequence of 2048 8-bit bytes.
security audit log file: A clusterwide file that
contains a record of security events on the system. Using the
ANALYZE/AUDIT command, you can produce reports and summaries of
security events from the security audit log file.
selective dump: A crash dump
containing only those portions of memory most likely to be useful in a
crash dump analysis. A selective dump is useful when sufficient disk
space is not available to hold all physical memory. Compare with
physical dump.
selective operation: A Backup utility operation that
processes files or volumes selectively, according to criteria such as
version number, file type, UIC, date and time of creation, expiration
date, or modification date.
sequential organization: On magnetic tape media, the
organization of data; that is, data is organized in the order in which
it is written to the tape.
server queue: A type of output execution queue that
uses a user-modified or user-written symbiont to
process the files that belong to print jobs in the queue. Compare with
printer queue and terminal queue.
setup module: A device control module
inserted at the beginning of a file in a print job.
shareable image: An image linked with the /SHAREABLE
qualifier of the Linker utility; it must subsequently be linked into an
executable image to be used. Shareable images are sometimes referred to
as linkable images.
shared image: A known image for which
more than one user can access the read-only and non-copy-on-reference
read/write sections of the image concurrently, so that only one copy of
those sections ever needs to be in physical memory.
shared resource: In an OpenVMS Cluster environment, a
resource (such as a disk or a queue) that any node in the cluster can
access. Data files, application programs, and printers are some items
that can be accessed by users on a cluster with shared resources,
without regard to the particular node on which the files or program or
printer might physically reside.
site-independent startup command procedure: A command
procedure that executes each time a system boots, and manages startup
of a system. This file, named SYS$STARTUP:STARTUP.COM, is required on
all systems, regardless of site-specific requirements. Do not
modify this file. Compare with site-specific startup
command procedure.
site-specific startup command procedure: A command
procedure that executes each time a system boots. Unlike the
site-independent startup command procedure, you can
add commands to site-specific procedures to perform operations that
vary from site to site.
sizing: The process of matching the allocation of
system resources (memory and disk space) with the workload requirements
of your site. Use the AUTOGEN command procedure to automatically size
your system.
slicing: On Alpha systems, a feature that lets the
operating system split the contents of images and sort the pieces so
that they can be placed with other pieces that have the same page
protection in the same area of memory. Consequently, translation
buffers on Alpha systems are used more efficiently than if the loadable
executive images or the shareable images were loaded in the traditional
manner.
source disk: In the command procedures VMSINSTAL.COM
or VMSKITBLD.COM, the disk from which you copy files. Compare with
target disk.
spooled printer: A printer set up to write output to
an intermediate storage device (such as a disk). Spool printers if your
system runs applications that write or copy data directly to printers
rather than submitting print jobs to a queue. In this way, printers
remain available to other system users while the program is running.
startup database: A file that contains information
used to start up system software. For example, the
site-independent startup command procedure uses
information in a startup database named STARTUP$STARTUP_VMS to start
the operating system. It uses information in a startup database named
STARTUP$STARTUP_LAYERED to start layered products.
swap file: In a swapping operation,
the file to which the system writes swapped portions of memory. Your
distribution kit includes a swap file named SYS$SYSTEM:SWAPFILE.SYS.
swapping: A memory management operation to efficiently
use the physical memory allotted to an entire system by moving
information between physical memory and files stored on disk. In
swapping, the system moves the entire workspace of a less active
process out of physical memory to a file. Compare with
paging.
symbiont: Used with an output queue, a process for formatting of print jobs and sending them to a printer.
The standard print symbiont provided by the operating system is named
PRTSMB and is designed to print files on basic output devices. The LAT
print symbiont LATSYM is used to print files on output devices attached
to a terminal server.
SYSGEN parameters: See system
parameters.
system area: One of two divisions of
CD-ROM volume space; includes logical sectors 0
through 15. Reserved for system use.
System Communications Services (SCS): In an OpenVMS
Cluster environment, software that implements intercomputer
communication, according to the Compaq Systems Communications
Architecture (SCA).
system disk: Disk on which operating system files are
stored.
system dump file: The file into which the operating
system writes the contents of the error log buffers, processor
registers, and memory when it detects an unrecoverable error or an
inconsistency within itself that causes the system to fail. See also
crash dump.
system image: An image that does not run under the
control of the operating system. It is intended for standalone
operation only. The content and format of a system image differs from
that of a shareable image and an executable
image.
system image snapshot: A record of the system setup
used with the Snapshot facility.
system messages: Messages returned by the system when
you enter commands in DCL or in utilities. These messages help you
understand the result of each command.
system parameters: Parameters for which you can set
values to control how the system functions. Values of system parameters
control a wide range of system functions including but not limited to
memory management, process scheduling, and system security.
system startup: Series of tasks that an operating
system does to start up the system.
system volume: A volume available to all the users on
a system. Compare to group volume.
systemwide logical name: A logical name that applies
to the entire system. It is defined in the system logical name table
and can be used by any process in a system.
tape mass storage control protocol (TMSCP) server: In
an OpenVMS Cluster environment, the component that implements the TMSCP
protocol, which is used to communicate with a controller for local MSCP
tapes, such as TU-series tapes. In conjunction with the tape class
device driver (TUDRIVER), the TMSCP server implements
this protocol on a processor, allowing the processor to function as a
storage controller.
Previous | Next | Contents | Index |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6017PRO_108.HTML
|