The Adabas Transaction Manager component which contains all logic for managing the two-phase commit process for distributed transactions is referred to as the TM.
A TM is required for each instance of the operating system. Each TM runs as a service within an Adabas System Coordinator daemon. A TM can interact with peer TMs in other systems to provide distributed transaction integrity across systems.
Adabas Transaction Manager can also interact with the CICS Syncpoint Manager and with RRMS, enabling Adabas RMs (databases) to participate in distributed transactions that affect other database or file systems. The TM is invoked transparently on behalf of applications.
Parameters are used to control processing of the Transaction Manager. These parameters are described in Parameters.
For more information on Adabas Transaction Manager execution, refer to the Operations Guide.
For information about the Adabas System Coordinator, refer to the Adabas System Coordinator documentation. For information about configuring Adabas Transaction Manager and Adabas System Coordinator for different environments, refer to the Configuration Guide.
The Adabas Transaction Manager client proxy represents the application in two-phase commit processing and is referred to as the ATM client proxy. The ATM client proxy invokes the TM on behalf of the application and responds to the application according to the result.
A job or TP system that requires Adabas Transaction Manager services must execute alongside a TM running as a service within an Adabas System Coordinator daemon, executing in the same system and under the same Adabas SVC or ID table. For information about the Adabas System Coordinator, refer to the Adabas System Coordinator documentation.
For information on client controls, which control the operation of the ATM client proxy, refer to Parameters.
For more information on ATM client proxy execution, refer to the Operations Guide.
The TM uses a recovery file to store vital recovery information. The same recovery file is shared by all TMs operating in the same Adabas System Coordinator group. For more information refer to Restart and Recovery.
Adabas Transaction Manager Online Services can be used to perform the following activities:
set the parameters that control the way that Adabas Transaction Manager processes application jobs,
list distributed transactions,
display detailed status information,
view the status of TMs throughout the network,
display runtime statistics for any TM in the network.
Online Services can also be used to force selectively the termination of one or more transactions. In an emergency, a transaction can be flushed from the system and its resources released without regard for transaction integrity. If this happens, all available details of the transaction are stored in the TM’s recovery file and can be printed.
For more information see Online Services.
Operator commands are provided to control Adabas Transaction Manager operation. See section Operator Commands for more information.
