Version 7.5.1
 —  Adabas Transaction Manager Version 7.5.1 Release Notes  —

Operational Changes and Enhancements

This section describes the operational changes and enhancements provided by Version 7.5.1.


Required System Coordinator Daemon

With ATM 7.5, an ATM daemon requires the presence of an Adabas System Coordinator (SYSCO) daemon executing locally under the same Adabas router. The System Coordinator enables multi-systems compatibility, including dynamic transaction routing and Sysplex support, with truly dynamic configuration capabilities. This allows Adabas Transaction Manager to be used very flexibly, across system images, whether Sysplex facilities are used or not. See also section TMNODES Parameter Now Redundant.

For more information, see ATM Daemons and Adabas System Coordinator Groups.

Top of page

Embedded Recovery Database

The Adabas Transaction Manager daemon uses database files to store vital recovery information about incomplete transactions, and for other purposes. 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.

Top of page

DTP=ET Parameter Replaced by DTP=RM

The DTP=ET parameter setting provided with ATM version 7.4.2 is made redundant because of the full support for Adabas Cluster Services and Adabas Parallel Services. Where the parameter DTP=ET has been used, it should be changed to DTP=RM. For more information, see Distributed Transaction Support.

Top of page

Notification that RM Services are Active

Whenever a Resource Manager signs on to an ATM daemon for distributed transaction processing, an ATM124 message, "Signed on for DTP with ATM node nnnnn", is issued, regardless of the order in which the different components were activated. This message is a positive confirmation that the database is enabled as a resource manager.

Top of page

TMNODES Parameter Now Redundant

With Adabas Transaction Manager version 7.5, control over transactions that cross system boundaries is determined by the scope of the System Coordinator group with which the application and ATM daemon are associated. A network of peer ATM daemons is determined by the scope of the associated System Coordinator group; therefore, the TMNODES parameter setting provided with earlier versions of ATM is now redundant.

For more information, see ATM Daemons and Adabas System Coordinator Groups.

Top of page

Default LGRECNO Value Changed

The default value of the LGRECNO job parameter is now 0. This minimizes default memory requirements.

Top of page

Required Datasets

For a complete overview of the datasets required by ATM, see the section Required Datasets.

Top of page