TS/MP 2.5 System Management Manual

tokens in an SPI buffer by calling the SSPUT procedure and retrieve them from the buffer by
using the SSGET procedure.
transaction An operation or a series of operations that retrieves and updates information to reflect an exchange
of goods or services. In the process of retrieving and updating information, a transaction transforms
a database from one consistent state to another. The TMF subsystem treats a transaction as a
single unit; either all of the changes made by a transaction are made permanent (the transaction
is committed) or none of the changes are made permanent (the transaction is aborted).
Transaction
Application
Language (TAL)
A systems programming language with many features specific to stack-oriented Tandem NonStop
systems. See also pTAL.
transaction
backout
A TMF subsystem activity in which the effects of a partially completed transaction are canceled.
Transaction
Delivery Process
(TDP)
A multithreaded gateway process, part of the Remote Server Call (RSC) product, that runs on a
Tandem NonStop system. The TDP can be replicated and can manage many connections and
workstations at one time, as well as multiple sessions from each workstation.
transaction
identifier
A unique name that the TMF subsystem assigns to a transaction.
transaction log See audit trail.
transaction
management
The ability to coordinate transaction control functions, such as beginning and ending transactions,
committing or aborting transactions, and recovering transactions.
Transaction
Management
Facility (TMF)
subsystem
The major component of the NonStop TM/MP product, which protects databases in online
transaction processing environments. To furnish this service, the TMF subsystem manages database
transactions, keeps track of database activity through audit trails, and provides database recovery
methods. See also NonStop Transaction Manager/MP (NonStop TM/MP) and transaction.
transaction mode The operating mode of a requestor program between the execution of a BEGINTRANSACTION
procedure call or statement and the execution of the associated ENDTRANSACTION or
ABORTTRANSACTION call or statement.
transaction
processing
See online transaction processing (OLTP).
transaction
workload
The number of transactions to be processed by an online transaction processing application.
TRANSFER delivery
system
An information delivery system that allows organizations to move and manage information
efficiently within a single Tandem system or across a network of systems. The TRANSFER delivery
system supports communications between users, I/O devices, and processes in the Guardian
environment.
TSCODE The object code for the part of a GDSX process that is supplied by Tandem. TSCODE includes
generic routines and services that support the development of a multithreaded, fault-tolerant
front-end process. See also USCODE and Extended General Device Support (GDSX).
tuning The process by which a system manager allocates and balances resources for optimum system
performance.
UMP See unsolicited-message processing (UMP).
unsolicited
message
A message that is sent to a SCREEN COBOL program and includes application-dependent
information to be processed by the program. Although the program does not do anything to
initiate the message, the message must conform to the format defined by the program. The message
is sent first to the TCP. It contains a header with information that is used by the TCP and a body
with information that the TCP delivers to the SCREEN COBOL program.
unsolicited-message processing (UMP)
The feature that allows terminals running SCREEN COBOL requestors to accept and reply to
unsolicited messages sent to them by Guardian processes outside of the PATHMON environment.
USCODE The object code for the part of a GDSX process that is developed by the user to provide device
or access-method specifics such as control operations or data-stream translation. USCODE is
bound with TSCODE to produce an operational GDSX process. See also TSCODE and Extended
General Device Support (GDSX).
345