TS/MP 2.5 System Management Manual

double-byte
character set
(DBCS)
A character set, such as Tandem Kanji, that uses two bytes of data to represent a single character.
DSM See Distributed Systems Management (DSM).
dumb terminal See fixed-function terminal.
dynamic server A server process that the PATHMON process creates after a TCP or ACS subsystem process has
waited for a specified time period for a static server to become available. A dynamic server
process exists only as long as it is needed. See also static server.
EDIT file A source text file that can be augmented and modified by the user through a Tandem text editor
program such as TEDIT (PS Text Edit).
EMS See Event Management Service (EMS).
EMS log file See event log file.
Enscribe database
record manager
Tandem database management software that provides a record-at-a-time interface between servers
and a distributed database. See also NonStop SQL/MP.
event log file A file maintained by the Event Management Service (EMS) for logging of event messages.
Event Management
Service (EMS)
A part of DSM used to provide event collection, event logging, and event distribution facilities.
It provides for different descriptions of events for people and for programs, lets an operator or
application select specific event message data, and allows for flexible distribution of event
messages within a system or network. EMS has an SPI-based programmatic interface for reporting
and retrieving events. See also event message.
event message A special kind of SPI message that describes an event occurring in the system or network. Event
messages are collected, logged, and distributed by EMS. See also Event Management Service
(EMS).
Expand
networking
software
Tandem software that can connect up to 255 Tandem NonStop systems into a single network.
expandability See scalability.
Extended General
Device Support
(GDSX)
A Tandem product that facilitates communication between general I/O devices and a PATHMON
environment by acting as a front-end or a back-end process.
extensible
structured token
In the Subsystem Programmatic Interface (SPI), a token with a value that can be extended by
appending new fields in later releases. The token is accessed through reference to a token map
containing field-version and null-value information, allowing SPI to provide compatibility between
different versions of the structure. See also simple token and token (definition 2).
external
PATHMON process
See external process.
external process A process in a different PATHMON environment from the process with which it is communicating.
For example, suppose a TCP managed by PATHMON process $PMB requests a link to a server
process in a server class that is managed by PATHMON process $PMA. Both the TCP and
PATHMON process $PMB are external processes with respect to PATHMON process $PMA and
the server class managed by $PMA.
external server See external process.
external TCP See external process.
fault tolerance The ability of a Tandem NonStop system to continue processing despite the failure of any single
software or hardware component within the system.
field-characteristic clause
In SCREEN COBOL, an ordered set of characters that specify the characteristics of a screen field.
file identifier (file
ID)
In the Guardian environment, the portion of a file name following the subvolume name. In the
OSS environment, a portion of the internal information used to identify a file in the OSS file
system. The two identifiers are not comparable.
file name In the Guardian environment, the set of node name, volume name, subvolume name, and file
identifier characters that uniquely identifies a file. This name is used to open a file and thereby
332 Glossary