The Adabas Transaction Manager component which contains all logic for managing the two-phase commit process for global transactions is referred to as the Adabas Transaction Manager daemon.
An Adabas Transaction Manager daemon is required for each instance of the operating system. Each daemon executes in its own address space as a special kind of Adabas nucleus. An Adabas Transaction Manager daemon can interact with peer Adabas Transaction Manager daemons in other systems to provide global transaction integrity across systems. Adabas Transaction Manager can also interact with the CICS Syncpoint Manager and with RRMS, enabling Adabas databases to participate in global transactions that affect other database or file systems. Adabas Transaction Manager is invoked transparently on behalf of applications.
ADARUN parameters are used to control daemon processing. These parameters are described in the section Parameters.
For information on daemon execution, see section Operations.
Execution of an Adabas Transaction Manager daemon requires that an associated Adabas System Coordinator daemon be active and available. For information about the Adabas System Coordinator, refer to the Adabas System Coordinator documentation. For information about configuring ATM daemons and Adabas System Coordinator for different environments, see the section Configuration.
The transaction manager proxy represents the application in two-phase commit processing. Executing as a subroutine of the Adabas link module and functioning as a transparent application stub, the proxy invokes the Adabas Transaction Manager daemon on behalf of the application and responds to the application according to the result.
For information on proxy job parameters, see the section Parameters.
For information on proxy execution, see the section Operations.
The Adabas Transaction Manager daemon uses database files to store vital recovery information about incomplete transactions, and for other purposes. With previous versions of Adabas Transaction Manager, it was strongly recommended that these files be defined in a separate database, which was referred to as the recovery database. These files must now reside in the ATM daemon’s own database. There is no longer any need for a separate database to contain these files.
For more information see section 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 users and global transactions,
display detailed status information,
view the status of Adabas Transaction Manager throughout the network,
display runtime statistics for any ATM daemon 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 ATM daemon's database and can be printed.
For more information on Online Services, see section Online Services.
Operator commands are provided to control Adabas Transaction Manager operation. See section Operations for more information.
An Adabas Transaction Manager daemon can produce a diagnostic log that
uses a dual logging system. If a log file becomes full, the daemon closes that
log file and switches to the other one. Logs may also be switched by using the
operator command TM FEOFLOG. The JOBS library
contains the sample job ATMLPRNT that can be used to produce a formatted report
of the diagnostic log.
