TS/MP 2.5 System Management Manual

TM/MP that provides these features is the TMF subsystem. See also Transaction Management
Facility (TMF) subsystem.
NonStop
Transaction
Services/MP
(NonStop TS/MP)
A Tandem product that provides process management and link management functions for OLTP
applications on Tandem NonStop systems. NonStop TS/MP consists of the PATHMON process,
the ACS subsystem process, the PATHCOM process and interface, and the Pathsend procedures.
Together with NonStop Transaction Manager/MP (NonStop TM/MP), NonStop TS/MP forms
the foundation for Tandem’s open transaction processing services, including those provided by
the RSC and POET products, the NonStop TUXEDO system, and the Parallel Transaction Processing
(PTP) Services for the CICS API product. See also Pathway/TS and NonStop Transaction
Manager/MP (NonStop TM/MP).
NonStop TUXEDO
application
See NonStop TUXEDO transaction processing environment.
NonStop TUXEDO
native client
See native System/T client.
NonStop TUXEDO
server
A server process or program managed by the NonStop TUXEDO system administrative facilities.
See also Pathway server.
NonStop TUXEDO
system
Tandem’s implementation of the Novell, Inc., TUXEDO enterprise transaction processing system.
Major features of the NonStop TUXEDO implementation include the use of the Tandem core
services (Tandem NonStop Kernel, NonStop Transaction Services/MP, and NonStop Transaction
Manager/MP) to provide the Tandem fundamentals (scalability, availability, and manageability)
for TUXEDO applications. The NonStop TUXEDO system runs in the OSS operating environment
on Tandem NonStop systems. See also OSS environment.
NonStop TUXEDO
transaction
processing
environment
An environment that provides the API and transaction monitor functions of the Novell, Inc., TUXEDO
transaction processing system in addition to the benefits provided by the Tandem core services:
Tandem NonStop Kernel, NonStop Transaction Services/MP, and NonStop Transaction
Manager/MP. See also Pathway transaction processing environment.
OBEY command A command in a Tandem interactive interface, such as PATHCOM or the SCREEN COBOL Utility
Program (SCUP), that allows users to execute the commands in a command file. See also command
file.
object An entity that is subject to independent reference or control by one or more subsystems. Examples
of objects are devices, communications lines, processes, and files. In the PATHMON environment,
the types of objects referred to or controlled by PATHCOM are PATHMON, PATHWAY,
LINKMON, SERVER, TCP, TERM, PROGRAM, and TELL. The PATHWAY object, used with the
SET PATHWAY and STATUS PATHWAY commands, refers to an entire PATHMON environment.
The LINKMON object is only referred to, not controlled, by PATHCOM: that is, users can use
PATHCOM to obtain information about LINKMON processes but cannot use it to make any
changes in the configuration or state of those processes. See also PATHMON environment.
object attributes See attributes.
object file A file generated by a compiler, linker, or binder that contains machine instructions and other
information needed to construct the executable code spaces and initial data for a process. The
file can be a complete program that is ready for immediate execution, or it can be incomplete
and require linking with other object files before execution. Compilers for languages such as
COBOL produce object code. See also pseudocode file.
object type In the Subsystem Programmatic Interface (SPI) or in an interactive interface such as PATHCOM,
a category of objects to which a specific object belongs. Object types for PATHCOM include
PATHMON, PATHWAY, LINKMON, SERVER, TCP, TERM, PROGRAM, and TELL. The SPI interface
to the Pathway subsystem uses different names for some of these object types and defines additional
object types; for example, PM, LM, PROGTERM, and TCPTERM are object types in the SPI interface.
OLTP See online transaction processing (OLTP).
OLTP application See online transaction processing (OLTP) application.
online transaction
processing (OLTP)
A method of processing transactions in which entered transactions are immediately applied to
the database. The information within the database is readily available to all users through online
screens and printed reports. The transactions are processed while the requestor waits, as opposed
to queued or batched transactions, which are processed at a later time. Online transaction
336 Glossary