XACI Command Reference Manual

A file access system (FAP). Typically, a FAP does not support a transactional model;
however enscribe does support the local transaction model.
●
S
Superior Transaction Manager (STM)
A trasaction manager that performs all coordination between the TMs supporting the global
transaction.
System
A system in NonStop terms is a set up to 16 CPUs that have the same expand network address.
T
Transaction Manager (TM)
Transaction Manager manages the global transactions using a 2 phase commit process, either all
participants commit or all are rolled back. The client application defines the start and end of a
global transaction by calling methods (or remote methods) of the TM.
Local Transaction ID (TID)
Transaction Management Facility (TMF) unique identifier. A concatenated string with the format
node.cpu.#, where the node indicates the name of the system on which the transaction was
initiated. cpu is the number of processing core where the transaction was initiated, # a unique large
integer value by which the transaction can be identified for this node.cpu.
U - W
There are no entries for this section.
X
XABroker
The XABroker is a generalized mechanism which could be used by any XA client (server side) to
ensure all work done in the context of the same XA transaction (XID) is done in the context of the
same TMF transaction.
Global Transaction ID ( XID)
In the distributed transaction processing environment, many resource managers (RMs) might
operate in support of the same unit of work and it is called the global transaction. XID is mapped
by the XABroker to TID.
XACONFIG table
A data structure that contains information about all the XABrokers configured on that system. It