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.
Action<br />
Response 243<br />
Origin<br />
Open Systems<br />
A double allocation has been detected between two or more files or a file <strong>and</strong> the free space<br />
table.<br />
Mainframe Systems<br />
Check the meaning of the <strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> error code, if one is present. Otherwise,<br />
determine the status of the global transaction using Online Services. If the required action is<br />
not apparent, contact your <strong>Software</strong> <strong>AG</strong> technical support representative.<br />
Open Systems<br />
Run ADAVFY without any options to find out which parts of which files are affected. Contact<br />
your nearest support center with the output from ADAVFY.<br />
Mainframe <strong>and</strong> open systems<br />
Explanation The explanation for this response code varies, depending on whether you are using <strong>Adabas</strong><br />
on mainframe systems or <strong>Adabas</strong> on open systems.<br />
Mainframe Systems<br />
The <strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> (ATM) or client proxy received an unsolicited syncpoint<br />
request. The action taken or the status of the global transaction that was open is indicated by<br />
a subcode in the <strong>Adabas</strong> control block Additions 2 field, in the low-order (rightmost) two<br />
bytes.<br />
Subcode Explanation <strong>and</strong> Recommended Action<br />
1<br />
2<br />
3<br />
4<br />
5<br />
6<br />
7<br />
12<br />
The unsolicited syncpoint request was accepted. The status of the current global<br />
transaction is not known.<br />
Use Online Services to determine the status of the global transaction.<br />
The unsolicited syncpoint request was accepted. The client session’s global<br />
transaction has been committed.<br />
The unsolicited syncpoint request was accepted. The client session’s global<br />
transaction has been backed out.<br />
The unsolicited syncpoint request was accepted. The client session’s global<br />
transaction had mixed completion (partially backed out, partially committed).<br />
The unsolicited syncpoint request was accepted. The client session’s global<br />
transaction is in backout.<br />
The unsolicited syncpoint request was accepted. The client session’s global<br />
transaction is in commit.<br />
The unsolicited syncpoint request was accepted. The client session had no global<br />
transaction open.<br />
The unsolicited syncpoint was attempted, but ATM returned response code 148<br />
(ADARSP148) so the outcome is not known.<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
<strong>Adabas</strong> Response <strong>Codes</strong><br />
159