HP OpenVMS Systems Documentation

If you have network access to another OpenVMS system (especially a timesharing system), you do not need to duplicate the example files distributed in the OpenVMS VAX or DECwindows Motif for OpenVMS VAX kits if they are available on the remote system. Similarly, remote access to the online documentation files also saves considerable disk space on any system with constrained disk space.

H.6 Managing Multiple Disk Systems

The following sections describe techniques for managing multiple disk systems. In addition to the goal of reducing the space requirements on the system device, it is possible to simultaneously reduce some of the I/O load to the system disk by redirecting necessary functions to an alternate device.

H.6.1 Alternate Page and Swap Files

Setting up alternate page and swap files is one of the best ways to reduce both the system disk space usage and I/O overhead. If you set up only a small primary page file on the system disk and install additional page and swap files in the startup command file SYS$MANAGER:SYPAGSWPFILES.COM, you can permanently cause these files to consume the least amount of space on the system device. For more information about setting up alternate page and swap files, refer to the OpenVMS System Manager's Manual.

H.6.2 Copying Dump Files

At startup, you can enhance the use of the paging file as a dump file that automatically copies the dump data for later analysis. This releases the disk space in SYS$SYSTEM:PAGEFILE.SYS to be used for paging automatically as well. Instead of manually invoking the System Dump Analyzer (SDA) to release the pages, you can add the following commands to the SYS$MANAGER:SYSTARTUP_VMS.COM file:

$ ANALYZE/CRASH SYS$SYSTEM:PAGEFILE.SYS
COPY alternate_disk:[dir]dumpname.ext
EXIT

There are several system logs and files that can be redirected to another device. For other system logs and files, it might be easier to reset and start a new log file, copy the old file or files to another device, and purge them from the system disk.

Some files that can be redirected are the system authorization file, the queue manager database, the audit log file, and batch log files. Some files that can be reset, copied, and purged are the operator log file, the accounting log file, and network log files. For more information about these facilities refer to the OpenVMS System Manager's Manual, the OpenVMS DCL Dictionary, or the utility reference manual for the utility whose files you want to offload.

H.6.4 Offloading Nonessential Files

Some of the files included with OpenVMS VAX Version 7.3 can be redirected to an alternate device during the installation or upgrade procedure. This can save many valuable system disk blocks while providing quick access to these files. For a small system disk configuration with multiple disks, this approach is recommended if you want the Help Message database to be available on line.

This glossary defines key terms in the context of an OpenVMS VAX computing environment.

boot, bootstrap: The process of loading system software into a processor's main memory. This guide uses the term boot to refer to this process.

boot command procedure: A program, stored on the console fixed disk, that is used to boot the OpenVMS operating system from a specified controller. Compaq provides a boot command procedure for each controller that the processor supports.

boot name: The abbreviated name of the boot command procedure you use to boot the system.

boot server: A VAX computer that is part of a local area OpenVMS Cluster system. The boot server is a combination of a MOP server and a disk server for the satellite system disk. See also satellite node.

CI-only cluster: A computer system consisting of a number of computers. It uses only the computer interconnect (CI) to communicate with other computers in the cluster. These computers share a single file system.

computer interconnect (CI): A type of I/O subsystem. It links computers to each other and to HSC devices. See also Hierarchical Storage Controller (HSC) device.

DECW$TAILOR: A software program that lets you add or remove DECwindows files from your system disk.

device name: The name used to identify a device on the system. A device name indicates the device code, controller designation, and unit number.

disk server: A computer within a local area cluster that provides an access path to CI, CSSI, and locally connected disks for other computers that do not have a direct connection.

Hierarchical Storage Controller (HSC) device: A self-contained, intelligent, mass storage subsystem that lets computers in a cluster environment share disks. Examples are the HSC50 and the HSC70.

HSC drive: Any disk or tape drive connected to an HSC device is called an HSC drive. A system disk on an HSC drive can be shared by several computers in an OpenVMS Cluster environment.

InfoServer: A general-purpose disk storage server that allows you to use the distribution compact disc to install the operating system on remote client systems connected to the same local area network (LAN).

local area OpenVMS Cluster system: A configuration consisting of one or more computers that act as a MOP server and disk server, and a number of low-end computers that act as satellite nodes. The local area network (LAN) connects all of the computers. These computers share a single file system.

local drive: Any drive that is connected directly to a computer. If you have a standalone computer, it is likely that all drives connected to the system are local drives.

media: Any packaging agent capable of storing computer software (For example, compact discs, magnetic tapes, floppy disks, disk packs, and tape cartridges.)

MOP server: A computer system running DECnet software that downline loads OpenVMS Cluster satellites using the DECnet maintenance operations protocol.

OpenVMS Cluster environment: A computer system consisting of two or more VAX or Alpha computers. There are four types of OpenVMS Cluster environments: CI only, DSSI only, local area, and mixed-interconnect.

satellite node: A computer that is part of a local area cluster. A satellite node is downline loaded from a MOP server and then boots remotely from the system disk served by a disk server in the local area cluster. See also boot server, disk server, MOP server.

save set: The format in which the Backup utility stores files. The OpenVMS operating system is shipped in this format.

scratch disk: A blank disk or a disk with files you no longer need.

source drive: The drive that holds the distribution kit during an upgrade or installation.

spin up, spin down: To spin up means to bring a disk drive up to operating speed; to spin down means to bring it gradually to a stop.

standalone BACKUP: A subset of the BACKUP utility that is booted into main memory instead of running under the control of the OpenVMS operating system. Standalone BACKUP is used to back up and restore the system disk and to install OpenVMS operating system software.

standalone system: A computer system consisting of just one computer.

system disk: The disk that contains or will contain the OpenVMS operating system. An OpenVMS system disk is set up so that most of the OpenVMS files can be shared by several VAX computers. In addition, each computer has its own directory on the system disk that contains its page, swap, and dump files.

target drive: The drive that holds the system disk during an upgrade or installation, or the drive you designate when backing up the system disk.

transaction log: A log used by DECdtm services to record information about transactions. The Log Manager Control Program (LMCP) is used to create a transaction log.

UETP (User Environment Test Package): A software package that tests all the standard peripheral devices on your system, various commands and operating system functions, the system's multiuser capability, DECnet software, and the cluster environment.

VMSTAILOR: A software program that lets you add or remove optional OpenVMS files from your system disk.