17.12.2012 Views

Adabas Response Codes - Software AG Documentation

Adabas Response Codes - Software AG Documentation

Adabas Response Codes - Software AG Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table of Contents<br />

<strong>Response</strong> 143<br />

Origin Open systems only<br />

Explanation A requested lock could not be granted because a deadlock situation has been detected.<br />

Action If the operation already performed in the current transaction have produced a new,<br />

useful and consistent database state, you should perform an end of transaction.<br />

Otherwise you should backout the transaction.<br />

<strong>Response</strong><br />

144<br />

Origin Mainframe and open systems<br />

Explanation One of the following occurred:<br />

The ISN specified with an update (A1) command was not in hold status for the<br />

user and command option H was not specified.<br />

An ET or BT command specifying the M (multifetch) option specified an ISN in<br />

the ISN buffer that is not in hold status for the user. All currently held ISNs are<br />

released from hold status.<br />

In this case on open systems, the first 2 bytes of the Additions 2 field (in binary<br />

format) contain the offset of that ISN in the ISN buffer.<br />

Action Put the ISN in hold status before using the A1 command or the multifetch ET or BT<br />

commands.<br />

<strong>Response</strong><br />

145<br />

If <strong>Adabas</strong> Transaction Manager is in use, verify that the setting for the Transaction<br />

Model parameter is appropriate for the program that was executing and is also<br />

appropriate for the runtime environment in use.<br />

Origin Mainframe and open system<br />

<strong>Adabas</strong> <strong>Response</strong> <strong>Codes</strong><br />

61

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!