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.

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

4<br />

Explanation The meaning of 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 />

This response code can only occur with a BT or ET command. The BT or ET command<br />

executes successfully. One of the following has occurred, depending on the subcode:<br />

Subcode Meaning<br />

1 <strong>Adabas</strong> attempted to hold an ISN already being held by another user.<br />

2 The number of ISNs as specified in the ISN buffer was too large<br />

compared to the ISN buffer length (ET or BT command with the M<br />

option).<br />

4 ISN is not on hold during multifetch ET/BT. ET/BT has successfully<br />

executed the ISNs so far released. The remaining ISNs are still on hold.<br />

5 An RI command with ISN=0 could not release from hold status all<br />

records held by the user, as requested, because one or more records had<br />

been updated earlier in the same transaction. Updated records cannot be<br />

released from hold status prior to transaction end. All records that had not<br />

been updated have been released from hold status.<br />

Open Systems<br />

The required function has not been executed completely. For an OP command with<br />

command option 2 = E or for an RE command, the specified record buffer length was<br />

shorter than the length of the ET data read. The record buffer has been truncated.<br />

For an A1//N1/N2 command, a descriptor value with the TR option is larger than 1144<br />

bytes. In this case, only the first 1144 bytes are stored in the index. Search operations<br />

for truncated values may be inexact since only the first 1144 bytes are evaluated. The<br />

first 2 bytes of the Additions 2 field contain the number of descriptor values truncated,<br />

the third and fourth bytes contain the field name of the descriptor value that is<br />

truncated.<br />

For an S1/S2/S4/S9 command, the resulting ISN list may not represent the exact result:<br />

this is because the search values and the values in the database were truncated after<br />

1144 bytes during the search operation of an S1/S2/S4 command and during the sort<br />

operation of an S2/S9 command.<br />

Action The method of resolving the error varies, depending on whether you are using <strong>Adabas</strong><br />

on mainframe systems or <strong>Adabas</strong> on open systems.<br />

Open Systems<br />

Table of Contents<br />

For an OP or RE command, increase the record buffer length or ignore the warning.<br />

For an S1/S2/S4/S9 command, either perform a post-selection using the complete field<br />

values, perform your own sort operation using the complete field values, or ignore the<br />

warning.

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

Saved successfully!

Ooh no, something went wrong!