TS/MP System Management Manual (G06.24+, H06.03+)

Glossary
NonStop TS/MP System Management Manual—541819-001
Glossary-7
EDIT file
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.
Enable product. A tool provided by Tandem that allows users to develop simple data
management applications without using a conventional programming language. The
Enable product can generate SCREEN COBOL programs for use with Enscribe
databases.
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).
expandability. See scalability.
Expand networking software. Tandem software that can connect up to 255 Tandem
NonStop systems into a single network.
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.