This section provides an overview of the enhancements provided with this release.
Amended Prefix for Transaction Management Service Operator Commands
Rename of client runtime control “Emergency Serial ET Commands”
Rename of client runtime control “Use Client-Side Transaction Manager”
Replacement for client runtime control “Use Host System Transaction Manager”
Replacement for client runtime control “Transaction Control”
Rename of client runtime controls “Generate External Syncpoint on ET/BT/CL Command”
Replacement for client runtime control “Application Controls ET Data”
Increase in TM parameter default value for RRMS concurrency processing
With Version 8.2, the prefix for the transaction management service operator commands is ATM and not TM like in previous versions.
The following messages are new or have been enhanced; an explanation of all messages is in the Messages and Codes section.
This enhanced message now displays the first 5 incomplete global transactions which are stopping the Transaction Manager from closing down during normal termination. The messages are repeated every 60 seconds until the incomplete transactions are resolved.
This new informational message indicates when the Transaction Manager close down process has ended.
This new informational message is issued by a transaction manager approximately five minutes after start-up and hourly thereafter. It displays a list of known databases and peer transaction managers.
This new informational message is issued by a
DTP=RM database that is initializing. The nucleus is
waiting for connection to the local Transaction Manager for distributed
transaction processing.
This new warning message is issued when a database is started with
ADARUN DTP=TM. This method of identifying a Transaction
Manager is no longer applicable.
The text in these messages has changed, however the circumstances when these messages are issued have not changed.
This new error message indicates a problem with the recovery file has been encountered.
These new informational messages are related to the agent processing which may follow the abnormal termination of a transaction manager. For more information refer to Transaction Manager failover.
Messages issued by the Adabas Transaction Manager service now include the node number (in the Adabas network) of the System Coordinator daemon under which it is running. This helps you understand origin of messages more clearly, especially if you run multiple nodes in a large system. The new message format appears as:
ATMnnn ss xxxxx MESSAGE TEXT
where xxxxx is the node number; nnn is the message number and ss is the severity.
The fix display in SYSATM has been enhanced to include a short description of each fix that is applied which helps you to get a better understanding of each fix that is in use.
The option to display local sessions has moved. It now appears within an integrated System Coordinator session display for all sibling products together such as Fastpath, Vista, Transaction Manager in the System Coordinator current activity display.
The new client runtime control "Adabas transaction dynamics" replaces "Transaction model" and enhances it with the following additional capability:
An "Adabas dynamic commits" count is maintained of those Adabas transactions which persist across TP message-pairs (displayed on the job/session statistics screen within the System Coordinator current activity display function).
Prevention of Adabas transactions persisting across TP message-pairs with a response 240 sub-code 596. An "Adabas dynamic backouts" count is maintained for such preventions (displayed on the job/session statistics screen within the System Coordinator current activity display function).
For more information about this control refer to Adabas transaction dynamics in the Adabas Transaction Manager Parameters documentation.
The client runtime control "Emergency Serial ET commands" has been renamed to "Continuous operation mode". For more information about this control refer to Continuous operation mode in the Adabas Transaction Manager Parameters documentation.
The client runtime control "Transaction model" has been replaced with the new client runtime control "Adabas transaction dynamics". No configuration file conversion is necessary. For more information about this control refer to Adabas transaction dynamics in the Adabas Transaction Manager Parameters documentation.
The client runtime control "Use Client-Side Transaction Manager" has been renamed to "Open distributed transaction support". For more information about this control refer to Open distributed transaction support in the Adabas Transaction Manager Parameters documentation.
The client runtime control "Use Host System Transaction Manager" has been replaced with the new client runtime control "Open distributed transaction support". Conversion to the new runtime control is done automatically the first time SYSCOR is entered. For more information about this control refer to Open distributed transaction support in the Adabas Transaction Manager Parameters documentation.
The client runtime control "Transaction Control" has been replaced with the new client runtime control "Transaction control by other vendors". No configuration file conversion is necessary. For more information about this control refer to Transaction control by other vendors in the Adabas Transaction Manager Parameters documentation.
The client runtime controls "Generate External Syncpoint on ET/BT/CL Command" have been renamed to "Transaction control by ET/BT/CL". For more information about these controls refer appropriately to Transaction control by ET, Transaction control by BT, Transaction control by CL in the Adabas Transaction Manager Parameters documentation.
The transaction manager statistics have been improved to include differentiating between those transactions that required full two phase commit processing and those transactions that didn’t. In addition, statistics relating to the recovery file are now also provided. For more information about these improvements refer to Statistics in the Online Services documentation.
The Copy ET Data utility program has been replaced with the new ET data management feature. This feature is provided as part of tasks in the System Coordinator network discovery function.
The client runtime control "Application Controls ET Data" has been replaced with the new client runtime control "ET data storage location". No configuration file conversion is necessary. For more information about this control refer to ET data storage location in the Adabas Transaction Manager, Parameters, Client Runtime Controls documentation.
The TM parameter default value for RRMS concurrency processing has been increased from 10 to 100 in order to be more tolerant of high-end systems. For more information about this control refer to Concurrency in the Adabas Transaction Manager, Parameters, TM Parameters documentation.