This glossary provides definitions for major terms used within Adabas Transaction Manager.
A set of software components that provides common interfaces and services for use by products such as Adabas Transaction Manager, Adabas Fastpath and Adabas Vista.
A set of software components that manages the process of committing global transactions across Adabas databases on behalf of clients to ensure global transaction integrity.
See Adabas Transaction Manager.
The server component of ATM. This component of ATM executes as a service within the Adabas System Coordinator daemon and provides transaction coordination and restart/recovery logic.
The process of removing the changes made as part of a global transaction that has not completed (synonymous with roll back).
See transaction branch.
A software component that executes as a subroutine of an Adabas link module and interfaces with Adabas Transaction Manager on behalf of each client session.
Parameters that govern the behavior of the ATM client proxy for a particular client session or job, or the behaviour of an ATM transaction manager with respect to the client session or job.
The successful completion of a transaction. After commit, all actions by resource managers on behalf of the transaction are guaranteed to be durable (permanent), even if any parts of the system fail.
In terms of Adabas: end of transaction
(ET).
The process of either backing out or committing a prepared global transaction.
See also back out, roll back, rollback, commit, global transaction, and prepare.
An abbreviation for Adabas System Coordinator.
A group of one or more Adabas System Coordinator daemons that together provide services to a related group of application jobs or other software components.
The execution of business transactions that are allowed to extend over multiple resource managers. A DTP system implies the use of two-phase commit processing and typically consists of application programs, resource managers, and a transaction manager per system image.
See distributed transaction processing.
The method of committing global transactions that relies on the two-phase commit protocol (see also serial mode).
See dynamic transaction routing.
A unique but reusable identifier assigned to a client session by the transaction manager for internal use.
A load balancing and availability function, offered by some application environments, which allows client sessions to migrate from one address space to another, possibly in a different operation system image.
A complete unit of work involving a number of actions performed by one or more resource managers. A transaction must be atomic (performed completely or not at all), consistent, isolated from other transactions, and (once it has been completed) durable.
See also transaction.
The list of active transactions that the ATM transaction manager maintains. It contains an entry for:
each active transaction in the local system; and
each active transaction branch belonging to a remote client session.
Parameters that govern the behavior of the ATM client proxy for a particular client session or job, or the behaviour of an ATM transaction manager with respect to the session or job.
In a configuration that includes more than one operating system instance, an ATM transaction manager must execute in each system that is to participate in distributed transaction processing. The transaction managers are referred to as partner ATM transaction managers.
Persistent recovery record file. See recovery record file.
The first phase of the two-phase commit process, during which target databases arrive at a recoverable state from which they can either commit or roll back the changes they have made as part of a global transaction.
A file in the ATM transaction manager's recovery file that contains recoverable details of active transactions that have not fully completed.
A software component that is responsible for managing changes to a set of resources. Typically, an RM is an instance of a database management system (DBMS).
See resource manager.
The process of removing the changes made as part of a global transaction that has not completed (synonymous with back out). After a rollback, all actions by resource managers on behalf of the transaction have been undone.
In terms of Adabas: back out transaction
(BT).
The method of transaction control that relies on a series of single-phase commit operations to secure a global transaction. This protocol does not guarantee global transaction integrity.
See also DTP mode.
See suspect transaction journal file.
A file in the transaction manager's recovery file that contains details of incomplete transactions that have been purged from the transaction manager memory by operator intervention or by using Online Services.
The point in a transaction at which the decision to commit or back out takes place.
An abbreviation for Adabas System Coordinator daemon – a software component that executes in its own address space and provides services to ATM and other software components.
A central file store, managed by a group of SYSCO daemons, for use by other software components, such as ATM transaction managers.
See transaction manager.
A complete unit of work involving a number of actions performed by one resource manager. A transaction must be atomic (performed completely or not at all), consistent, isolated from other transactions, and (once it has been completed) durable. See also global transaction.
A part of a global transaction that is managed as a subordinate unit of the transaction as a whole. A transaction that crosses system boundaries has a branch on each affected system that is remote from the client; the ATM transaction manager on each of these systems manages the corresponding transaction branch on behalf of the ATM transaction manager that is local to the user.
A unique identifier of a global transaction. Also known as XID.
A software component that is responsible for coordinating transactions that change resources controlled by more than one resource manager.
A software component that executes as a subroutine of an Adabas link module and interfaces with Adabas Transaction Manager on behalf of each client session.
A type of Adabas command that affects or is related to the processing of global transactions.
The feature of Adabas Transaction Management that makes it possible for an application program to benefit from global transaction integrity without being aware of the two-phase commit process.
A protocol for ensuring the integrity of global transactions.
A request to commit or back out a global transaction that is issued by some software component without involving the application’s ATM client proxy.
See transaction identifier.
