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.

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

Action<br />

Response 23<br />

Origin<br />

Explanation<br />

66<br />

Subcode Meaning<br />

42<br />

50<br />

51<br />

52<br />

53<br />

1005<br />

1006<br />

1007<br />

1008<br />

1009<br />

1010<br />

1011<br />

1012<br />

1013<br />

1015<br />

On open systems, for an A1 comm<strong>and</strong> with comm<strong>and</strong> option 2 = 'T', the current<br />

time is still the same as the value of the field with SY=TIME in the database.<br />

The Router (LCC) detected an invalid comm<strong>and</strong> code. This may also arise when a<br />

new ACBX-type call is presented to a back-level router.<br />

A client call with the ADARUN parameter PREFETCH=OLD has multiple APLX<br />

buffers or the contents of APLX+4(chained APLX) is non-zero. To resolve this,. use<br />

the ADARUN parameter setting PREFETCH=YES.<br />

A non-<strong>Adabas</strong> target was called.<br />

Invalid file specified for an <strong>Adabas</strong> Online System function.<br />

The comm<strong>and</strong> code is invalid.<br />

The ACBX is invalid (not first buffer).<br />

The ABD is invalid.<br />

The ABD type is invalid.<br />

More than one search buffer specified.<br />

More than one value buffer specified.<br />

More than one ISN buffer specified.<br />

The number of search <strong>and</strong> value buffers do not match.<br />

The number of format <strong>and</strong> record buffers do not match.<br />

A streaming logic error occurred.<br />

Correct the comm<strong>and</strong> code or comm<strong>and</strong> option or the previous OP comm<strong>and</strong>, <strong>and</strong> rerun the<br />

program.<br />

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

An invalid starting ISN was specified for an L2/L5 comm<strong>and</strong> sequence:<br />

■ The ISN was not assigned to a record in the file; or<br />

■ The ISN was greater than the MAXISN in effect for the file.<br />

Open Systems<br />

On open systems the following subcodes may occur:<br />

<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>

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

Saved successfully!

Ooh no, something went wrong!