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 />
Response 221<br />
Origin<br />
Mainframe systems only<br />
Explanation The LU size of the remote partner is smaller than the size required for the <strong>Adabas</strong> request.<br />
Action<br />
Either increase the size specified for the LU= parameter on the remote system, or modify the<br />
application to reduce its buffer sizes.<br />
Response 222 - 223 (reserved)<br />
Response 224<br />
Origin<br />
Mainframe <strong>and</strong> open systems<br />
Explanation An <strong>Adabas</strong> comm<strong>and</strong> has been timed out by Entire Net-Work. The request waited for a reply<br />
for a longer time period than specified by the REPLYTIM parameter in either the Entire<br />
Net-Work NODE statement or the SET operator comm<strong>and</strong>. The reply may be delayed or lost<br />
due to a target malfunction, or because of a connecting link failure. If you are using Natural,<br />
<strong>and</strong> all connections are verified, check the ADAMODE setting. The ADAMODE=0 setting is<br />
the only option Entire Net-Work supports.<br />
Action<br />
Response 225<br />
Origin<br />
Subcode Meaning<br />
1076<br />
An XTS timeout error occurred.<br />
Check the node <strong>and</strong> remote database or contact your database administrator for assistance.<br />
Mainframe <strong>and</strong> open systems<br />
Explanation A comm<strong>and</strong> was issued from a server, such as an <strong>Adabas</strong> nucleus, to another server, such as<br />
Entire Net-Work. The comm<strong>and</strong> did not complete within a prescribed time period. The issuer<br />
proceeds <strong>and</strong> no longer expects a response to the comm<strong>and</strong>.<br />
Action<br />
156<br />
Note that the comm<strong>and</strong> may still execute in the target. There will be no notification to the<br />
issuer if it does. The target may display message ADAM92, User Gone, if the target attempts<br />
to notify the issuer of comm<strong>and</strong> completion.<br />
The subcode identifies the environment from which the comm<strong>and</strong> was issued.<br />
Subcode Issuer<br />
1<br />
2<br />
3<br />
ADAMPM<br />
<strong>Adabas</strong> nucleus, thread-synchronous comm<strong>and</strong><br />
<strong>Adabas</strong> nucleus, not thread-synchronous. Under z/OS, the comm<strong>and</strong> was<br />
TCB-synchronous.<br />
Contact your <strong>Software</strong> <strong>AG</strong> technical support representative for assistance if the reason for<br />
the comm<strong>and</strong>'s failure to complete cannot be identified.<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>
Change language