Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - Software AG ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Adabas</strong> Response <strong>Codes</strong><br />
64<br />
Subcode Meaning<br />
8<br />
9<br />
10<br />
11<br />
12<br />
13<br />
14<br />
15<br />
16<br />
17<br />
18<br />
19<br />
21<br />
22<br />
23<br />
24<br />
The comm<strong>and</strong> is invalid for an ET user in preliminary ET status. First complete the<br />
transaction using <strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong>.<br />
The current user is not authorized to issue an ET/BT comm<strong>and</strong>.<br />
The C2 comm<strong>and</strong> is no longer permitted.<br />
The C3 comm<strong>and</strong> can only be issued by EXU users.<br />
The L1/4 comm<strong>and</strong> with the option "F" is not valid for exp<strong>and</strong>ed files.<br />
The call issued is not permitted when the database is in a suspend state.<br />
Invalid privileged comm<strong>and</strong>.<br />
An L1/L4 comm<strong>and</strong> specified the multifetch option ("M" or "O") was not combined<br />
with either the "I" or "N" option.<br />
The user does not have "privileged" comm<strong>and</strong> authorization.<br />
Not permitted during online save.<br />
Applications using the ADALNK X'48' call logic receive this response when the<br />
logic has been suppressed.<br />
On mainframe systems, a special utility comm<strong>and</strong> was issued for an obsolete<br />
subfunction.<br />
On open systems, an ET or BT with comm<strong>and</strong> option "S" was issued without<br />
subtransactions being enabled for the current <strong>Adabas</strong> user session by specifying<br />
comm<strong>and</strong> option "S" in the OP comm<strong>and</strong>.<br />
One of the following occurred:<br />
■ A BT comm<strong>and</strong> was issued by a non-ET logic user.<br />
■ An ET comm<strong>and</strong> was issued for a distributed transaction managed by <strong>Adabas</strong><br />
<strong>Transaction</strong> <strong>Manager</strong>; ET comm<strong>and</strong>s are invalid for a distributed transaction<br />
managed by <strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong>.<br />
The current transaction has already been heuristically terminated or the comm<strong>and</strong><br />
is not allowed within an MC sequence.<br />
One of the following occurred:<br />
■ The last MC subcomm<strong>and</strong> is not ET.<br />
■ A BT comm<strong>and</strong> was issued for a distributed transaction managed by <strong>Adabas</strong><br />
<strong>Transaction</strong> <strong>Manager</strong>; BT comm<strong>and</strong>s are invalid for a distributed transaction<br />
managed by <strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong>.<br />
One of the following occurred:<br />
■ An ET or CL comm<strong>and</strong> with user data is not allowed for read-only access to a<br />
database.<br />
■ CL is invalid because the user has a transaction in progress that is managed by<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong>.<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>
Change language