Adabas Transaction Manager Messages and Codes - Software AG ...

Subcode Meaning
26
62
63
64
66
67
68
73
74
The user's command was routed to a different cluster nucleus than the one used by
previous commands. Some cluster nucleus terminated abnormally while the new
nucleus was creating a new session for the user.
Action: Restart the Adabas session with a new OP command.
An OP (open) command was issued without a user/ET ID, which is required for
this type of application or environment.
Action: Correct the program to specify a user/ET ID, and rerun the program.
An OP command was given for an ET user not in ET status. The user is backed out
with an Adabas-generated BT command, and the operation is closed.
Action: Repeat the OP call.
An OP command was issued with an 8-byte ET ID that already exists.
An Adabas session with OPENRQ=YES was active and the user issued an Adabas
command without having issued an OP command.
Action: Ensure that all users issue an OP command as the first Adabas command.
Insufficient Work part 1 space for open command with ETID definition when trying
to read the user profile.
The user queue element has been deleted. Most likely the command was thrown
back due to ISN contention or space shortage. The space shortage is normally
workpool space; if this is the case, the LWP parameter setting should be increased.
This subcode is issued by Adabas Transaction Manager.
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.
This subcode is issued by Adabas Transaction Manager.
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.
Adabas Transaction Manager Messages and Codes
Adabas Response Codes
53