OpenVMS System Manager's Manual

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

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

target disk: In VMSINSTAL.COM or VMSKITBLD.COM, the disk to which you move the system files. Compare with source disk.

terminal queue: A type of output execution queue that uses a symbiont to direct output to a terminal printer. Compare with printer queue and server queue.

terminal servers: Communication devices dedicated for connecting terminals, modems, or printers to a local area network (LAN) and to other systems within a LAN. See also LAT protocol.

time differential factor (TDF): Difference between local system time and Coordinated Universal Time (UTC). See also Coordinated Universal Time.

track: On a disk, the collection of sectors (or blocks, on Files-11 volumes) at a single radius on one recording surface of the disk. It is accessible to a given read/write head position on the disk device.

trailer labels: On magnetic tape, labels similar to header labels, but written following the file.

transaction group: A group of computers involved in DECdtm transactions whose SCSNODE names must obey specific rules.

transaction log: a file that stores information about DECdtm transactions performed on a node. It is of file type .LM$JOURNAL.

trusted logical names: Logical names associated with executive mode or kernel mode.

tuning: The process of altering various system values to obtain the optimum overall performance possible from any given configuration and work load.

UAF: See user authorization file (UAF).

UETP (User Environment Test Package): A software package designed to test whether the OpenVMS operating system is installed correctly.

UIC: See user identification code (UIC).

UIC-based protection: A protection mechanism based on the user identification code (UIC) and applied to all protected objects. Compare with access control list (ACL).

update procedure: Procedure used if you have a previous version of the operating system and you want to make minor fixes to it. When you update the operating system, the update procedure replaces some system files.

upgrade procedure: If you are already running a standard version of the operating system, you can use the upgrade procedure to obtain a higher version.

user authorization file (UAF): A file containing an entry for every user that you authorize to gain access to the system. Each entry identifies the user name, password, default account, UIC (user identification code), quotas, limits, and privileges assigned to individuals who use the system.

User Environment Test Package (UETP): See UETP.

user identification code (UIC): The pair of numbers assigned to users, files, and other system objects, that specify the type of access available to the owner, group, world and system. The UIC consists of a group number and a member number separated by a comma and enclosed within square brackets. Same as UIC. See also account and UIC-based protection.

user mode: The least privileged processor access mode. User processes and run-time library routines run in user mode.

UTC: See Coordinated Universal Time.

utility program: A program supplied by Digital that performs a set of related operations. For example, the Backup utility (BACKUP) allows you to save and restore files.

VAXcluster satellite: In a Local Area VAXcluster configuration, a VAXcluster computer without a local system disk. A VAXcluster satellite uses disks and tapes locally connected to a VAXcluster server.

VAXcluster server: In a Local Area VAXcluster configuration, a VAXcluster node that uses the mass storage control protocol (MSCP) server and tape mass storage control protocol (TMSCP) server software to make its locally connected disks and tapes available to VAXcluster satellites over the local area network (LAN).

VAXcluster system: A loosely coupled configuration of two or more VAX computers and storage subsystems. A VAXcluster system appears as a single system to the user, even though it shares some or all of the system resources. When a group of VAX computers shares resources in a VAXcluster environment, the storage and computing resources of all the computers are combined, which can increase the processing power. See also OpenVMS Cluster system.

VAXport drivers: In a VAXcluster environment, device drivers that control the communication paths between local and remote ports. (Examples are PADRIVER for the CI, PEDRIVER for the LAN, and PIDRIVER for the DSSI.)

vector: On VAX systems, a group of related scalar values, or elements, all of the same data type.

vector-capable systems: On VAX systems, those systems that comply with the VAX vector architecture.

vector consumer: On VAX systems, a process requiring the vector capability and having a vector context.

vector-present processor: On VAX systems, an integrated scalar-vector processor pair, included in a VAX vector processing system configuration.

virtual device server: Serves physical device media and sets of logical disk blocks to client systems in a local area network (LAN). Systems running the appropriate client software can connect to virtual devices as though they are locally attached devices. A virtual device server does not impose a file system on the virtual devices that it serves. See also InfoServer system.

virtual device unit: With an InfoServer system, a virtual device that represents the local OpenVMS context for a volume that resides on a remote server.

Virtual disk units have a device name in the DADn: format. Virtual tape units have a device name in the MADn: format.

See also binding, InfoServer system, and virtual device server.

volatile database: On a node in a network, a working copy of the DECnet configuration database that reflects current network conditions. Contrast with permanent database.

volume: Disk or tape media that has been prepared for use by creating a new file structure on it and mounting it on a device.

volume set: A collection of disk volumes bound into a single entity by the DCL command MOUNT/BIND. To users, a volume set looks like a single, large volume.

Also, the volumes on which a set of multivolume files is recorded.

volume space: Set of all logical sectors on a volume containing information about the volume.

writable image: A known image for which a shared non-copy-on-reference writable section is removed from physical memory (for paging reasons or because no processes are referencing it), and it is written back to the image file.

write lock: A device becomes write-locked when a hardware or user error occurs while a disk or magnetic tape volume is mounted for a write operation. For example, if a disk is write-locked or a tape is missing a write ring, the hardware generates an error.

  6017P078.HTM
  OSSG Documentation
  22-NOV-1996 14:23:13.05

Legal