| 75 |
A commit operation involving an external transaction coordinator
failed. ATM attempted to back out the transaction.
Check the external transaction coordinator for the reason. Check
for error messages from ATM daemons or the ATM proxy of the failing
job.
|
| 76 |
An error occurred while an ATM daemon was attempting to rebuild the
transaction hierarchy of a user who has migrated from another ATM daemon’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 daemons or the ATM proxy of the failing
user.
|
| 77 |
This message indicates that the user 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 daemons and
clustered application environments in the COR group.
|
| 78 |
It was not possible to commit the user’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 user 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 daemon address space caused the
current global transaction to be backed out.
Increase the amount of memory available to the ATM daemon, restart
it, then restart the transaction.
|
| 82 |
A memory shortage occurred in the ATM daemon address space, and ATM
attempted to back out the current global transaction.
Increase the amount of memory available to the ATM daemon, 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 the user’s ETID. This is possible,
for example, if a user survives a restart of the ATM daemon. For an
RE command, this subcode will be returned if the
user is known to ATM but has no ETID.
The user must 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.
|
| 89 |
One of the following occurred:
-
An attempt was made to back out the global transaction because,
after a period of inactivity, a new user session was started with the same
ETID. In this case, close the user session.
-
A user who was executing under the CICS Resource Manager
Interface had an incomplete transaction when the CICS system terminated, and
the transaction was backed out during restart of the CICS system. In this case,
repeat the transaction, if desired.
|
| 90 |
The ATM proxy detected either an inconsistency between its view of
the user’s status and the ATM daemon’s view, or that the ATM daemon had
restarted. It attempted to back out on all target databases.
Close the user’s sessions and start them again.
|
| 91 |
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. 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 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 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 user’s transaction was controlled by an external transaction
coordinator, which reported that the transaction has been backed out.
Restart the transaction.
|
| 96 |
The user’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 proxy
detected that the user’s Task Interface Element (TIE) was being used by another
user.
If this condition occurs when running Natural in such a way that
two Adabas sessions are maintained for each user, ensure that Natural zaps
NA44231 and NA45010 are applied (both are present in Natural v3.1.6). Further,
if the user executes with TRANMODE=MESSAGE, ensure that
Natural will issue an OP command for its system
session; for example, supply a non-blank ETID, or use the Natural
DBOPEN parameter. If the error persists, contact your
Software AG support representative.
|
| 98 |
The user 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 user incurred a security response code; ATM backed out the
user’s changes.
If security permissions are not adequate, correct them and rerun
the transaction.
|
