Availability Guide for Application Design

Glossary
Availability Guide for Application Design—525637-004
Glossary-4
command file
command file. A file that serves as a source for command input. For example, users can
prepare a command file containing PATHCOM or COBOL Utility Program (SCUP)
commands. They can then cause the commands in the file to be executed by issuing
the PATHCOM or SCUP OBEY command and specifying the name of the file.
Alternatively, they can specify this file as the input file when they execute PATHCOM or
SCUP.
Common Run-Time Environment (CRE). An environment for running D-series mixed-
language programs.
communications controller. A hardware component that manages communications lines
or devices.
communications subsystem. An HP product that provides users with access to a set of
communications services. Some examples of communications subsystems are
Expand, HP TCP/IP, and Multilan.
complex instruction-set computing (CISC). A processor architecture based on a large
instruction set, characterized by numerous addressing modes, multicycle machine
instructions, and many special-purpose instructions. Contrast with reduced instruction-
set computing (RISC).
concurrency control. Protection of a database record from concurrent access by more
than one process. The TMF product imposes this control by dynamically locking and
unlocking affected records to ensure that only one transaction at a time accesses
those records.
configuration file. In a NonStop Tuxedo system, contains all the information necessary to
start a NonStop Tuxedo application.
configuration management. The process of configuring the production system hardware
and software to adapt to changes.
consistency. See database consistency
.
consumer distributor. An Event Management Service (EMS) distributor process that
returns selected event messages to management applications upon request. See also
forwarding distributor
, printing distributor, and Event Management Service (EMS).
context. Information required by a server to process the current request in an exchange of
multiple request and reply messages: for example, identification of the last item
processed. See also context-free server.
context-free server. A server that does not retain any information about the processing of
previous requests. See also context.
control-state information. Information provided by a primary process to a backup process
that operates as the other half of a process pair. This information provides the backup