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

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

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

Response 29<br />

Origin<br />

Explanation<br />

Action<br />

Response 34<br />

Origin<br />

Explanation<br />

Action<br />

Response 35<br />

Origin<br />

Explanation<br />

Action<br />

Response 39<br />

Origin<br />

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

In an L3 or L6 comm<strong>and</strong>, a value repositioning was attempted (bytes 3-8 of the Additions 1<br />

field contain spaces) <strong>and</strong> the Comm<strong>and</strong> Option 2 field did not contain the value "A", "D", or<br />

"V". The comm<strong>and</strong> ID is released.<br />

Correct the Additions 1 or Comm<strong>and</strong> Option 2 field.<br />

Mainframe systems only<br />

An invalid comm<strong>and</strong> option has been detected.<br />

Depending on the subcode in the rightmost two bytes of the ACB's Additions 2 field or the<br />

ACBX's Error Subcode (ACBXERRC) field, one of the following has occurred:<br />

Subcode Meaning<br />

1<br />

2<br />

9<br />

An invalid comm<strong>and</strong> option has been specified in one of the comm<strong>and</strong> option fields.<br />

The R option has been specified for the C5 comm<strong>and</strong>, but replication is not active.<br />

A record buffer must be specified for this comm<strong>and</strong> but is missing (not specified<br />

of length zero).<br />

Either remove the invalid comm<strong>and</strong> option or replace it with a valid option.<br />

Mainframe systems only<br />

The user/DBA attempted to perform a function for a noncluster <strong>Adabas</strong> nucleus that is<br />

available only for an <strong>Adabas</strong> cluster database.<br />

Either perform the function against a cluster database or change the function.<br />

Mainframe systems only<br />

Explanation A logically deleted descriptor was used as a search criterion or was specified in the first two<br />

bytes of the Additions 1 field for an L3, L6, L9, S2, or S9 comm<strong>and</strong>.<br />

Action<br />

Remove the use of the logically deleted descriptor <strong>and</strong> inform your database administrator<br />

about the problem.<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 />

69

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

Saved successfully!

Ooh no, something went wrong!