TMF Glossary (G06.26+)

TMF Glossary
HP NonStop TMF Glossary—522415-003
Glossary-11
multi-threaded process
multi-threaded process. An application process that can deal with more than one TMF
transaction concurrently. A multi-threaded requester, for example, can initiate more
than one transaction concurrently and switch from one transaction to another.
Similarly, a multi-threaded server can accept multiple work requests concurrently (for
one or more transactions) and switch from one work request to another.
N
network transaction. See distributed transaction.
network-distributed transaction. See distributed transaction.
node. In the NonStop Kernel operating system environment, a node is a system that is part
of an Expand network. The name of the node, also called the system name, is the first
of four parts of the fully qualified filename. The node name is preceded by a backslash
(\); for example, \SANFRAN.
nonaudited file. A disk file that is not flagged for protection by TMF. TMF does not control
where a nonaudited file resides, so the file can exist on an audited volume or any other
volume.
NonStop SQL. A relational database management system that provides efficient online
access to large distributed databases. The main components of NonStop SQL are a
data dictionary; the SQL language for definition, manipulation, and control of data; a
programmatic interface; a conversational interface; a report writer; and a set of utilities.
NonStop Transaction Services/MP (TS/MP). A product that provides process
management and link management functions for OLTP applications on NonStop
systems. NonStop TS/MP consists of the PATHMON process, the LINKMON process,
the PATHCOM process and interface, and the Pathsend procedures. Together with
TMF, NonStop TS/MP forms the foundation for the HP open transaction processing
services, including those provided by the RSC and POET products, and the NonStop
TUXEDO system. See also Pathway/TS
.
O
OBEY command file. A file that serves as a source for command input. Command files are
prepared using a standard text editor. When such an input file is invoked, TMFCOM
reads and executes each command in the file sequentially: this can be done either
through the OBEY command or by specifying the command file as the input file when
you run TMFCOM.
offline backup. A static copy of a database file (audited or not audited) written to secondary
storage media (such as tape) while the database is inactive (TMF may be running, but
no transactions are being processed). You can use an offline backup to recover a
database to the time that the backup was made, but you cannot recover the database
to the current time. Contrast with online backup.