This glossary defines key terms in the context of an OpenVMS
computing environment.
A |
---|
Advanced Server for OpenVMS | | Supported on OpenVMS Alpha systems only, an OpenVMS-based network
operating system compatible with Microsoft networking technology.
Allows OpenVMS systems to be file and print servers for Windows
desktop users. These users can use Microsoft products and utilities
such as Windows Explorer to access file and print resources. Also
provides a flexible system for network administration and security.
This product supports OpenVMS ODS-5 disk volumes and Extended File
Specifications. See also PATHWORKS for Advanced Server (OpenVMS).
|
---|
Availability Manager | | A system management tool that enables the system
manager to monitor one or more OpenVMS nodes on an extended LAN
from an OpenVMS, Windows 2000, or Windows XP system. Availability
Manager helps system managers and analysts target a specific node
for analysis. The tool collects system and process data from multiple
nodes simultaneously; it analyzes the data and displays the output.
The Availability Manager (base) software installed with OpenVMS
provides the data collection components that allow the system to
be monitored by the Availability Manager and by DECamds.
|
---|
B |
---|
Baseboard Management Controller (BMC) | | A utility provided with HP Integrity servers that allows
you to control some management features built into the system board,
such as diagnostics, configuration, and hardware management. It enables
you to interact with the Extensible Firmware Interface (EFI) and
to boot the OpenVMS operating system. See also Extensible Firmware Interface (EFI), Management Processor
(MP).
|
---|
BIB | | Boot-is-blocked. The state of a cell (on a cell-based
Integrity server) that is powered on but not allowed to boot. When
all cells assigned to an nPartition are at the BIB state, the nPartition
is inactive and no software can run on the nPartition until it is
manually booted past BIB. See also cell, nPartition.
|
---|
boot server | | A boot server downloads the system software required
by a client system. A TCP boot server (TCP/IP Services for OpenVMS
BOOTP server) is the host that centralizes configuration and management
of an IP address database, such as is used for OpenVMS InfoServer
client booting and satellite booting. For satellite booting, the
boot server is part of an OpenVMS Cluster; it includes either a
MOP server (for OpenVMS Alpha systems) or a BOOTP/TFTP server (for
OpenVMS I64 systems), and a disk server for the satellite system disk. See also InfoServer, satellite node.
|
---|
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.
|
---|
C |
---|
cell | | Also known as a cell board: a circuit board that is
the basic building block of an nPartition in a server complex (such
as any HP midrange and high-end Integrity servers). A cell consists
of a symmetric multiprocessor and memory. See also cell-based server, nPartition (node partition), server complex,
virtual partition.
|
---|
cell-based server | | A hardware complex that can run one or more operating
systems and that supports dividing hardware resources into nPartitions.
All processors and memory are contained in cells, each of which
can be assigned for exclusive use by an nPartition. See also cell, nPartition (node partition), server complex,
virtual partition.
|
---|
CI-only cluster | | A computer system consisting of several computers
attached to a computer interconnect (CI) through which it communicates with
other computers in the cluster. These computers share a single
file system. CI provides redundant paths. See also DSSI-only cluster.
|
---|
Common Data Security Architecture (CDSA) | | A multiplatform, Open Source security infrastructure.
CDSA provides a stable, standards-based programming interface that
enables applications to access operating system security services.
With CDSA, you can create cross-platform, security-enabled applications. Beginning
with Version 2.2, CDSA includes support of Secure Delivery and HRS
(Human Recognition Service Standard). CDSA is automatically installed
with the operating system. For more information about CDSA, see
the HP Open Source Security for OpenVMS, Volume 1: Common Data Security Architecture manual. See also Secure Delivery, HRS (Human Recognition Service Standard).
|
---|
complex | | See server complex..
|
---|
computer interconnect (CI) | | A type of I/O subsystem. It links computers to
each other and to HSx devices (for example, an HSJ or HSG).
|
---|
concurrent upgrade | | The entire OpenVMS Cluster is shut down and unusable
while upgrading each system disk. When the cluster reboots, all
cluster members start up the upgraded version of the OpenVMS operating
system.
|
---|
core | | The actual data processing engine within a cell-based
processor. A single processor can have multiple cores. Also referred
to as a logical CPU.
|
---|
core I/O | | Provides the base set of I/O functions required
by every nPartition on a cell-based Integrity server. Includes
the partition console interface and the network interface. See also cell, cell-based server, nPartition.
|
---|
D |
---|
DECnet Phase IV | | Networking software that allows OpenVMS systems
to participate in network task-to-task communications to transfer
and copy files, print files, and run applications. DECnet Phase
IV networking capabilities are defined in the DIGITAL Network Architecture
(DNA) Phase IV. A system-integrated product (SIP), DECnet for OpenVMS
I64 is a component of the Foundation Operating Environment (FOE)
on the Integrity servers license bundle. See also DECnet-Plus, TCP/IP Services for OpenVMS.
|
---|
DECnet-Plus | | Formerly known as DECnet/OSI, DECnet-Plus is the
networking software that offers the capabilities defined in the
DIGITAL Network Architecture (DNA) Phase V protocols. DECnet-Plus provides
the newest DECnet features such as extended addressing and downline-load
performance enhancements. DECnet-Plus integrates DECnet and OSI
protocols and provides a linkage to TCP/IP. DECnet-Plus for OpenVMS
I64 is a component of the Foundation Operating Environment (FOE)
on the Integrity servers license bundle. See also DECnet Phase IV, TCP/IP Services for OpenVMS.
|
---|
DECwindows Motif for OpenVMS | | A layered product that provides support for both
OSF/Motif, a standards-based graphical user interface, and the X user
interface (XUI) in a single, run-time and development environment.
DECwindows Motif displays the OSF/Motif user interface, but applications
written on either toolkit will run regardless of the environment
selected by the user.
|
---|
device name | | The name used to identify a device on the system.
A device name indicates the device code, controller designation,
and unit number, such as DKA0, where DK is the device code, A is
the boot device controller designation, and 0 is the unit number
on the boot device.
|
---|
diagnostic partition | | When present on an OpenVMS I64 system disk, this
partition corresponds to the contents of SYS$MAINTENANCE:SYS$DIAGNOSTICS.SYS
on the disk. The diagnostic partition and its contents are intended
and reserved for use by HP Services. Customer access and use is
not supported.
|
---|
disk server | | A computer within a local area cluster that provides
an access path to CI, DSSI, and locally connected disks for other
computers that do not have a direct connection.
|
---|
DSSI-only cluster | | A computer system consisting of several computers
attached to a Digital Storage System Interconnect (DSSI) through
which it communicates with other computers in the cluster. These
computers share a single file system. DSSI is a medium-bandwidth
interconnect that OpenVMS Alpha nodes can use to access peripherals
(such as disks and tapes). See also CI-only cluster.
|
---|
E |
---|
encryption | | A process implemented for data confidentiality that
converts sensitive or otherwise private data to an unintelligible
form called cipher-text. Decryption reverses the process, taking the
unintelligible cipher-text and converting the data back into its
original form, called plaintext. Encryption and decryption are also
known as encipher and decipher. Encryption for OpenVMS software
is based on the Advanced Encryption Standard (AES) alogrithm and
is integrated with the operating system. This allows OpenVMS users, system
managers, security managers, or programmers to secure their files,
save sets, or application data with AES Encryption.
|
---|
Enterprise Operating Environment (EOE) | | The tier of the Operating Environment for OpenVMS
for Integrity Servers that offers everything offered by the Foundation
Operating Environment (FOE) plus system management capabilities
and volume shadowing. See also Operating Environments (OE) for OpenVMS for Integrity
Servers, Foundation Operating Environment (FOE), and Mission Critical Operating
Environment (MCOE).
|
---|
EOE | | See Enterprise Operating Environment (EOE)..
|
---|
Extensible Firmware Interface (EFI) | | The interface between HP Integrity server operating system
and system firmware enabling you to perform such tasks as configuring
the firmware and controlling the booting environment. EFI is the Intel
specification of an interface between firmware and hardware. See also Baseboard Management Controller (BMC), Management
Processor (MP), Pre-OS System Environment (POSSE).
|
---|
F |
---|
FOE | | See Foundation Operating Environment (FOE)..
|
---|
Foundation Operating Environment (FOE) | | The tier of the Operating Environment for OpenVMS
for Integrity Servers that offers the base operating system and
networking transport products. The contents of this tier are contained
in each of the other, higher-level tiers. See also Operating Environments (OE) for OpenVMS for Integrity
Servers, Enterprise Operating Environment (EOE), and Mission Critical
Operating Environment (MCOE).
|
---|
H |
---|
HRS (Human Recognition Service Standard) | | HRS provides generic authentication service suitable
for use with any form of human authentication (biometrics) for operation
with CDSA. See also Common Data Security Architecture (CDSA).
|
---|
HSx device | | A self-contained, intelligent, mass storage subsystem
(for example, an HSJ or HSG) that lets computers in a cluster environment
share disks.
|
---|
HSx drive | | Any disk or tape drive connected to an HSx device
(for example, an HSJ or HSG). A system disk on an HSx drive
can be shared by several computers in an OpenVMS Cluster environment.
|
---|
Hyper-Threading | | Supported on systems that have dual-core processors,
this feature provides the ability for processors to create a second
virtual core that allows additional efficiencies of processing.
For example, a dual-core processor with Hyper-Threading active can
run four threads.
|
---|
I |
---|
InfoServer | | A general-purpose disk storage server (virtual device
server). It can make devices available to client systems on the
LAN. Client systems can connect to the virtual devices and use them
as though they are locally attached devices. OpenVMS systems connected
to the same LAN can boot from a virtual drive available from the InfoServer
instead of from a local CD or DVD.
|
---|
instance | | See OpenVMS instance..
|
---|
Instant Capacity (iCAP) | | Supported on cell-based Integrity servers, an HP
Utility Pricing Solutions product whose pricing model is based on
purchasing components (processors, cell boards, and memory). Instant
Capacity allows you to purchase and install additional components
at a discount from the regular purchase price, as the usage rights
are not included. These Instant Capacity components are inactive
but installed and ready for use. When extra capacity is needed,
you pay the remainder of the regular purchase price for the usage
rights (through purchasing a Right to Use codeword) to activate
the components. (If the regular price for the component is reduced
by the time the usage rights are purchased, the remainder price
is proportionally reduced, providing additional savings.) After obtaining
usage rights, Instant Capacity processors can be turned on by the
Instant Capacity software or during installation. Previous versions of iCAP were referred to as Instant Capacity
on Demand, or iCOD. See also Pay per use (PPU), Temporary Instant Capacity (TiCAP).
|
---|
Integrated Lights-Out (iLO) | | See Management Processor (MP)..
|
---|
K |
---|
Kerberos | | A network authentication protocol that provides
authentication for applications using secret-key crytpography.
Kerberos is automatically installed with the OpenVMS operating system.
|
---|
L |
---|
layered products | | Products (including system-integrated products)
provided by HP and third parties that can installed on an OpenVMS system. See also system-integrated product (SIP).
|
---|
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 LAN connects all of the computers.
These computers share a single file system.
|
---|
local drive | | A drive, such as a CD, DVD, or disk 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.
|
---|
logical CPU | | An execution thread contained within a core on a
cell-based integrity server. With Hyper-Threading enabled, each
core can contain multiple logical CPUs. See also core, Hyper-Threading.
|
---|
M |
---|
Maintenance Operations Protocol (MOP) | | A protocol used for operations such as downline loading
and upline dumping. See also MOP server.
|
---|
Management Processor (MP) | | A utility on HP Integrity servers that provides
both local and remote access for controlling the system console, reset/power
management, and transfer of control (TOC) capabilities. It also
allows you interact with the Extensible Firmware Interface (EFI)
and to monitor tasks and display detailed information about various
internal subsystems. MP is available even when the server main power
switch is in the off position. On entry-class Integrity servers,
MP is known as the Integrated Lights-Out (iLO) Management Processor. See also Baseboard Management Controller (BMC), Extensible
Firmware Interface (EFI).
|
---|
MCOE | | See Mission Critical Operating Environment (MCOE)..
|
---|
media | | Any packaging agents capable of storing computer
software (for example, compact discs, magnetic tapes, floppy disks,
disk packs, and tape cartridges).
|
---|
migration support | | In OpenVMS Clusters, migration support means that
HP has qualified the versions for use together in configurations
that are migrating in a staged fashion to a newer version of OpenVMS
VAX, OpenVMS Alpha, or OpenVMS I64. Problem reports submitted against
these configurations are answered by HP. However, in exceptional
cases HP might request moving to a warranted configuration as part
of the solution. Migration support helps customers move to warranted
OpenVMS Cluster pairs. See also warranted support.
|
---|
Mission Critical Operating Environment (MCOE) | | The tier of the Operating Environment for OpenVMS
for Integrity Servers that offers everything offered by the Enterprise
Operating Environment (EOE) plus clustering. See also Operating Environments (OE) for OpenVMS for Integrity
Servers, Foundation Operating Environment (FOE), and Enterprise
Operating Environment (EOE).
|
---|
MOP server | | A computer system using either the LAN Auxiliary
Control Process (LANACP) or DECnet software to downline-load systems
using the Maintenance Operations Protocol (MOP). Systems loaded
include OpenVMS systems, print servers, and LAT servers. See also Maintenance Operations Protocol (MOP).
|
---|
N |
---|
nPartition (node partition) | | A hard partition within a cell-based server that
provides both hardware and software isolation among different instances
of the operating system running on a single server. Cell-based
servers can be configured either as a single, large, symmetric multiprocessor or
as several independent systems. An nPartition has exclusive use
of the memory, processor, and I/O resources belonging to the cells
that are assigned to that partition, and can execute its own operating system
image. See also cell, partition, server complex, virtual partition).
|
---|
O |
---|
OE | | See Operating Environments (OEs) for OpenVMS for Integrity
Servers..
|
---|
OpenVMS Cluster system | | A computer system consisting of two or more Alpha,
VAX, or Integrity server computers running HP OpenVMS Cluster software.
Many types of cluster interconnect devices can be used to create
a cluster environment; for example, CI, DSSI, and LAN devices in
a local area network, and Shared Memory CI (SMCI) for OpenVMS Galaxy
instances. An OpenVMS Cluster can consist of a single interconnect
or a mixed-interconnect cluster with any combination of cluster
interconnects.
|
---|
OpenVMS instance | | The OpenVMS operating system running in either a
soft or hard partition of a hardware platform. To share memory
in a hard partition, the GALAXY system parameter must be set.
|
---|
OpenVMS Management Station | | A powerful Microsoft Windows based management tool
for system managers and others who perform system management tasks
on OpenVMS systems. Allows system managers to manage user accounts,
printers, and storage across multiple systems, using an intuitive
interface that eliminates the need to remember complex OpenVMS DCL
syntax, command procedures, and device names. A server component
is installed on OpenVMS (automatically if you select all the default
values during the installation); a client component is installed
on a PC.
|
---|
Operating Environment (OE) DVD | | The DVD containing the OpenVMS for Integrity Servers
Operating Environment and operating system, and the installation
and other procedures described in this manual.
|
---|
Operating Environments (OEs) for OpenVMS for
Integrity Servers | | The model for delivering the OpenVMS I64 operating
system, layered products, and documentation. Each operating environment bundles
a group of products offered together at a single price based on
the number of active processor cores in the system. For
definitions of the three operating environments, see Foundation
(FOE), Enterprise (EOE), and Mission Critical (MCOE).
|
---|
operating system CD | | The CD containing the OpenVMS Alpha operating system
and the installation and other procedures described in this manual. See also operating system media, Operating Environment DVD.
|
---|
operating system media | | The operating system CD or the OE DVD included with
your OpenVMS distribution kit. See also operating system CD, Operating Environment DVD.
|
---|
P |
---|
partition | | A subset of the server hardware that includes processor,
memory, and I/O resources on which an operating system can run.
This type of partitioning allows a single server to run independently
an operating system in each partition with isolation from other
partitions. See also cell, nPartition, server complex, virtual partition.
|
---|
PATHWORKS for OpenVMS (Advanced Server) | | Supported on OpenVMS Alpha and VAX systems only,
an OpenVMS network operating system compatible with Microsoft networking technology.
Allows OpenVMS systems to be file and print servers for Windows
desktop users. Such users can use Microsoft products and utilities
such as Windows Explorer to access file and print resources. Also
provides a flexible system for network administration and security. See also Advanced Server for OpenVMS.
|
---|
Pay per use (PPU) | | Supported on cell-based Integrity servers and part
of the HP Utility Pricing Solutions program for customers who prefer
leasing systems from HP Finance. Pay per use provides CPU capacity
as needed, basing payment on actual metered or monitored use of
that capacity. You acquire a particular hardware platform and number of
processors, and are charged for usage of the processors based on
demand. PPU is intended for customers who would rather lease the
processors rather than purchasing them as would be done using Instant
Capacity (iCAP). See also Instant Capacity (iCAP), Temporary Instant Capacity
(TiCAP).
|
---|
Performance Data Collector (TDC) | | The Performance Data Collector for HP OpenVMS (TDC) collects
and manages configuration and performance data for analysis by other
applications. TDC_RT Version 2.2 or higher is a run-time only (base) variant
of the TDC software that is installed automatically with the OpenVMS
operating system for use on specific operating system platforms.
By default, data is collected in a file. Subsequently, user applications
can retrieve the data from the file.
|
---|
platform | | A PCSI utility concept in which the OpenVMS operating
system is kitted with options for selected other products (for example, DECwindows
Motif and networking products) so that the user can opt to install
all at once. Generically, a platform is the combination of physical
hardware and operating system on which a piece of management or
application software runs.
|
---|
Pre-OS System Environment (POSSE) | | The HP implementation of EFI that extends the EFI
Shell and EFI Boot Manager to include additional features for managing
hardware and system boot options. See also Extensible Firmware Interface (EFI).
|
---|
R |
---|
rolling upgrade | | Each system disk in an OpenVMS Cluster is upgraded
individually, allowing old and new versions of the operating system
to run together. Certain members of the cluster are available for
use while others are being upgraded. See also concurrent upgrade.
|
---|
S |
---|
satellite node | | A computer that is part of a local area cluster.
A satellite node is downline loaded from a boot server and then
boots remotely from the system disk served by a disk server in the
local area cluster. See also disk server, boot server.
|
---|
scratch disk | | A blank disk or a disk with files you no longer
need.
|
---|
Secure Delivery | | Supported by CDSA, Secure Delivery uses public key
and digital signature technology to implement a system that provides OpenVMS
users the ability to validate files from OpenVMS and third-party
OpenVMS vendors. The validation process involves authenticating
the originator and verifying the contents of a file. Secure Delivery
is integrated into PCSI to automatically ensure that software installed
on OpenVMS was not tampered with prior to installation. Most kits included
on the OpenVMS distribution media (as of Version 8.3) have been
signed using Secure Delivery. See also Common Data Security Architecture (CDSA).
|
---|
Secure Sockets Layer (SSL) | | The open-standard security protocol for secure transfer
of sensitive information over the Internet. HP SSL offers a high degree
of confidentiality by allowing server authentication, client authentication,
and an encrypted connection that requires all information sent between
client and server to be encrypted by the sending software and decrypted
by the receiving software. HP SSL for OpenVMS is automatically installed
with the OpenVMS operating system. For more information, see the HP Open Source Security for OpenVMS, Volume 2: HP SSL for OpenVMS manual.
|
---|
server complex | | The hardware of a cell-based server that includes
all cells, I/O expansion cabinets, cables, cabinet hardware, fans,
and power and utilities components. The complex can support multiple
instances of an operating system by means of nPartitions. See also cell, nPartition (node partition), server complex.
|
---|
SIP | | See system-integrated product (SIP)..
|
---|
source drive | | The drive that holds the operating system distribution
media during an upgrade or installation. This may be a local drive
or an InfoServer. The drive contains either the operating system
CD or DVD, or a copy of it.
|
---|
standalone system | | A computer system consisting of a single computer
that is not part of a network or OpenVMS Cluster.
|
---|
system disk | | The disk from which OpenVMS is booted. During an
installation or upgrade, this is the source drive. After installation,
the target drive is booted and becomes the system disk.
|
---|
system-integrated product (SIP) | | A product provided by HP that can be installed or
upgraded as part of the OpenVMS installation or upgrade. SIPs include
required products, such as CDSA, Kerberos, and the base kit for
Availability Manager, and optional products such as DECwindows Motif, DECnet-Plus,
DECnet Phase IV, TCP/IP Services for OpenVMS, and on OpenVMS I64
systems only, WBEM Services for OpenVMS. See also layered products.
|
---|
T |
---|
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.
|
---|
TCP/IP Services for OpenVMS | | HP standard implementation of the TCP/IP and NFS
networking protocols, integrated with the OpenVMS operating system
installation. Provides interoperability and resource sharing among
systems running OpenVMS, UNIX, Windows, and other operating systems
that support TCP/IP. TCP/IP provides a comprehensive suite of functions
and applications that support industry-standard protocols for heterogeneous network
communications and resource sharing. See also DECnet Phase IV, DECnet-Plus.
|
---|
TDC | | See Performance Data Collector..
|
---|
Temporary Instant Capacity (TiCAP) | | Supported on cell-based Integrity servers, an HP
product option included with Instant Capacity (iCAP) that enables you
to purchase prepaid processor activation rights for a specified
(temporary) period of time. Temporary capacity is sold in increments such
as 20-day or 30-day increments, where a day equals 24 hours for
a core. TiCAP was formerly referred to as TiCOD. See also Instant Capacity (iCAP), Pay per use (PPU).
|
---|
U |
---|
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 multiple-user capability, DECnet software, and the
cluster environment.
|
---|
V |
---|
virtual partition | | A soft partition within a cell-based server that
can provide software isolation among different instances of the
operating system running on a single server or nPartition. Cell-based servers
can be configured either as a single large symmetric multiprocessor
or as several independent systems. A virtual partition uses a subset
of the system processor, memory, and I/O resources, and includes
operating system and application-related software. The HP-UX operating
system is the only operating system that can run in a virtual partition. See also cell, partition, nPartition (node partition), server
complex.
|
---|
volume shadowing | | The software that performs disk mirroring operations
using a redundant array of independent disks (RAID) 1 storage strategy.
Provides high data availability for disk devices by ensuring against
data loss that results from media deterioration or controller or
device failure. This prevents storage subsystem component failures
from interrupting system or application tasks. Volume Shadowing
for OpenVMS is available as both a separately licensed product on
Integrity server systems and a component of the Enterprise Operating
Environment (EOE) on Integrity servers.
|
---|
W |
---|
warranted support | | In OpenVMS Clusters, warranted support means that
HP has fully qualified the specified versions of OpenVMS coexisting
in the cluster and addresses all problems identified by customers
using the cluster configuration. See also migration support.
|
---|
WBEM (Web-Based Enterprise Management) Services
for OpenVMS | | An optional product available on OpenVMS I64 systems
only that provides an industry-standard enterprise management framework
and resource description. WBEM’s structured framework is
capable of being extended and uses Internet standards. Developers
of management applications can take advantage of work previously
done to expose resource information and operations; for example,
developers can take code that was developed for a specific platform
or application and use it with WBEM for the same purposes. WBEMCIM
is the WBEM Services for OpenVMS file name used in the PCSI kit.
CIM stands for the Common Information Model, which differentiates
the current OpenVMS WBEM product from the original one that is based
on the Simple Network Maintenance Protocol (SNMP).
|
---|