13.12.2012 Views

Adabas Transaction Manager Messages and Codes - Software AG ...

Adabas Transaction Manager Messages and Codes - Software AG ...

Adabas Transaction Manager Messages and Codes - Software AG ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Response 2<br />

Origin<br />

Mainframe <strong>and</strong> open systems<br />

Explanation The meaning of this response code varies, depending on whether you are using <strong>Adabas</strong> on<br />

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

Action<br />

Mainframe Systems<br />

This response code can only occur with a BT or ET comm<strong>and</strong>. The BT or ET comm<strong>and</strong> executes<br />

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

Subcode Meaning<br />

1<br />

2<br />

4<br />

5<br />

Open Systems<br />

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

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

ISN buffer length (ET or BT comm<strong>and</strong> with the M option).<br />

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

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

An RI comm<strong>and</strong> with ISN=0 could not release from hold status all records held by<br />

the user, as requested, because one or more records had been updated earlier in the<br />

same transaction. Updated records cannot be released from hold status prior to<br />

transaction end. All records that had not been updated have been released from<br />

hold status.<br />

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

option 2 = E or for an RE comm<strong>and</strong>, the specified record buffer length was shorter than the<br />

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

For an A1//N1/N2 comm<strong>and</strong>, a descriptor value with the TR option is larger than 1144 bytes.<br />

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

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

Additions 2 field contain the number of descriptor values truncated, the third <strong>and</strong> fourth<br />

bytes contain the field name of the descriptor value that is truncated.<br />

For an S1/S2/S4/S9 comm<strong>and</strong>, the resulting ISN list may not represent the exact result: this is<br />

because the search values <strong>and</strong> the values in the database were truncated after 1144 bytes<br />

during the search operation of an S1/S2/S4 comm<strong>and</strong> <strong>and</strong> during the sort operation of an<br />

S2/S9 comm<strong>and</strong>.<br />

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

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

Open Systems<br />

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

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

perform your own sort operation using the complete field values, or ignore the warning.<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 />

49

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

Saved successfully!

Ooh no, something went wrong!