| 73 |
The client session had an externally-controlled transaction, the
outcome of which was “in doubt”. ATM forcibly resolved the “in doubt”
transaction. There is a possibility that ATM’s resolution of the transaction
might be inconsistent with the intended outcome.
Check that the outcome of the session’s Adabas changes, in its
previous transaction, was consistent with its changes to non-Adabas resources.
Check the external transaction coordinator for reasons why the
original transaction might have been left in the “in doubt” state. If the
external coordinator indicates that the transaction was completed, and if the
relevant system logs give no indication of the cause of the problem, contact
your Software AG support representative.
|
| 74 |
The client’s database session has lost its ETID. If a transaction
was in progress, ATM attempted to back it out from all affected databases and
release all held records.
Issue a new OP command to the
database.
|
| 75 |
Either a commit operation involving an external transaction
coordinator failed, or resynchronization with an external transaction
coordinator caused the transaction to be backed out. In the first case, ATM
attempted to back out the transaction.
For the first case, check the external transaction coordinator for
the reason. Check for error messages from ATM transaction managers or the ATM
client proxy of the failing job.
|
| 76 |
An error occurred while an ATM transaction manager was attempting
to rebuild the transaction hierarchy of a client session that has migrated from
another ATM transaction manager’s domain as a result of dynamic transaction
routing. ATM attempted to back out the transaction.
Check the status of the transaction using Online Services. Check
for error messages from ATM transaction manager or the ATM client proxy of the
failing user.
|
| 77 |
This message indicates that the client session had an open
transaction and has been migrated from one node to another within a cluster
(Sysplex), but ATM could not handle the transaction safely because no Migrated
Transaction Record (MTR) file had been defined. The transaction was therefore
backed out.
Define and create an MTR file, and restart the ATM transaction
managers and clustered application environments in the COR group.
|
| 78 |
It was not possible to commit the client session’s transaction
because of a pending ET syncpoint on a target
database. This could be because of a concurrent online save operation, database
termination, or a SYNCC operator command. Backout of
the incomplete transaction was attempted.
Restart the transaction when the pending
ET syncpoint has been completed.
|
| 80 |
The client session was not at ET status
in the target database. Backout of the incomplete transaction was
attempted.
Restart the transaction.
|
| 81 |
A memory shortage in the ATM transaction manager's address space
caused the current global transaction to be backed out.
Increase the amount of memory available to the ATM transaction
manager, restart it, then restart the transaction.
|
| 82 |
A memory shortage occurred in the ATM transaction manager's address
space, and ATM attempted to back out the current global transaction.
Increase the amount of memory available to the ATM transaction
manager, restart it, then restart the transaction.
|
| 83 |
An error occurred during a commit or backout operation for a global
transaction. ATM attempted to back the transaction out.
If the cause of the error is not apparent from console messages,
contact your Software AG technical support representative.
|
| 84 |
ATM reported conflicting use of an ETID. For an
RE command, this subcode can be returned if the
client is known to ATM but has no ETID.
The client should issue a CL command to
each open database; then re-open.
|
| 85 |
The global transaction time limit (TMGTT)
has been exceeded, and an attempt has been made to back out the global
transaction.
Correct the cause of the timeout, then restart the
transaction.
|
| 86 |
The global transaction time limit (TMGTT)
has been exceeded, and the global transaction has been backed out.
Correct the cause of the timeout, then restart the
transaction.
|
| 90 |
The ATM client proxy detected either an inconsistency between its
view of the client session’s status and the ATM transaction manager’s view, or
that the transaction manager had restarted. It attempted to back out on all
target databases.
Close the client’s sessions and start them again.
|
| 91 |
Transactions on a target database were being quiesced, or an
administrator issued a "stop" request for the session's transaction via ATM
Online Services or operator command, or there was a pending
ET syncpoint on the database. Backout of the
incomplete transaction was attempted.
Restart the transaction when all required target databases are
available.
|
| 92 |
Transactions on a target database were being quiesced, or an
administrator issued a stop request for the user via ATM Online Services or
operator command, or there was a pending ET
syncpoint on the database. The incomplete transaction was backed out.
Restart the transaction when all required target databases are
available.
|
| 93 |
An error occurred while ATM was attempting either to start a new
global transaction or to bring a new database into a transaction. The client
proxy backed out changes from all databases.
The next command issued returns details of the error that caused
the backout. Check the meaning of the response code and act
accordingly.
|
| 94 |
An error occurred while ATM was attempting either to start a new
global transaction or to bring a new database into a transaction. The client
proxy attempted to back out changes from all databases.
The next command issued returns details of the error that caused
the backout. Check the meaning of the response code and act
accordingly.
|
| 95 |
The client session’s transaction was controlled by an external
transaction coordinator, which reported that the transaction has been backed
out.
Restart the transaction.
|
| 96 |
The client session’s transaction was controlled by an external
transaction coordinator, which reported “backed out, outcome pending” for the
transaction. This means that backout has begun for the transaction, and will be
completed when all the resource managers involved in it are able to comply with
the backout request.
Restart the transaction.
|
| 97 |
The CICS Resource Manager Interface is in use, and the ATM client
proxy detected that the client session’s Task Interface Element (TIE) was being
used by another session.
This can occur if all of the following are true:
-
Natural is being used, in such a way that two Adabas sessions
are maintained for each client;
-
The client control Transaction Model is
set to MESSAGE;
-
Natural parameters are set such that Natural might not generate
OP commands for all database sessions.
You can make sure that Natural generates
OP commands by using a non-blank ETID, or by means
of Natural’s DBOPEN parameter.
The condition can also occur if all of the following are true:
-
Natural is being used, in such a way that two Adabas sessions
are maintained for each client;
-
The Adabas System Coordinator has timed out Natural’s “system”
session.
In this case, a new Natural LOGON might clear the condition.
Otherwise terminate the session and start a new session.
If the error persists, contact your Software AG support
representative.
|
| 98 |
The client session was executing in serial mode, and requested that
changes be committed. Some of the changes were committed, and some were backed
out.
Examine the results of the transaction. If necessary, correct the
result by manual intervention.
|
| 99 |
The client session incurred a security response code; ATM backed
out the user’s changes.
If security permissions are not adequate, correct them and rerun
the transaction.
|
