Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - Software AG ...
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> Response <strong>Codes</strong><br />
Action<br />
128<br />
Subcode Description<br />
266<br />
267<br />
268<br />
270<br />
297<br />
298<br />
299<br />
Open Systems<br />
A bad LB field value reference was encountered in a base file record. The base file<br />
is bad.<br />
An LB field value referred to in a base file record is not present in the LOB file.<br />
Probably, the base file <strong>and</strong> the LOB file are out-of-sync.<br />
Internal LOB update error. At the end of a LOB update in the LOB file, the LOB<br />
value reference or placeholder was not found in the associated base file record where<br />
it was expected. Possibly, the base file record was changed in parallel.<br />
Internal LOB update error. At the end of a LOB update in the LOB file, the base<br />
record was not in exclusive hold status anymore.<br />
A planned feature for large object (LB) fields (for example, character code conversion<br />
of LB field values) is not yet supported.<br />
Too many (more than 32,767) LB field occurrences were specified in the format<br />
buffer.<br />
An internal error occurred due to LOB file processing.<br />
LOB data processing may fail because of concurrent updates. If a new attempt to process the<br />
LOB data also fails, this response code is returned. The subcode (field ACBXERRC in the<br />
ACBX) provides more information:<br />
Subcode Description<br />
297<br />
300<br />
A planned feature for large object (LB) fields (for example, character code conversion<br />
of LB field values) is not yet supported.<br />
The referential integrity <strong>and</strong> uniqueness checks done by subtransactions are currently<br />
not compatible with comm<strong>and</strong>s that modify LOB values.<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 />
Mainframe Systems<br />
Resolve the problem described in the subcode list in the explanation.<br />
Open Systems<br />
If one of the subcodes above occurs, you must change the program that is making the <strong>Adabas</strong><br />
calls.<br />
If the subcode (field ACBXERRC in the ACBX) is not one of the subcodes mentioned above,<br />
<strong>and</strong> if the response code 132 is reproducible even though the accessed LOB fields are not<br />
being updated, contact your <strong>Software</strong> <strong>AG</strong> technical support representative.<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>
Change language