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.

Action<br />

Response 41<br />

Origin<br />

■ The terminating period was missing;<br />

■ The first position contains a period, this only applies to N1 or N2 comm<strong>and</strong>s;<br />

■ Length <strong>and</strong>/or format specified with a range definition;<br />

■ An invalid element was detected;<br />

■ A field segment notation was not correct: it must be specified either as<br />

(byte-number,length) or as (byte-number,length,length-2), where byte-number<br />

must be either "*" or a decimal number, <strong>and</strong> length <strong>and</strong> length-2 are decimal numbers.<br />

These numbers must be less than 2,147,483,648;<br />

■ A field segment notation was specified for a range of MU fields or for a range of fields<br />

within a periodic group.<br />

On open systems, the following information is returned in the Additions 2 field of the control<br />

block:<br />

■ The leftmost two bytes contain the number of the byte (in binary format) relative to the<br />

beginning of the format buffer where the error was detected.<br />

■ The rightmost two bytes contain the name of the field being processed when the error was<br />

detected.<br />

Correct the format buffer.<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 />

Mainframe Systems<br />

One or more specification errors exist in the format buffer. When possible, the short name of<br />

the field for which the error occurred is stored at offset 2 of the ACB's Additions 2 field or in<br />

the ACBX's Error Character Field (ACBXERRB).<br />

The following specification errors may have been made:<br />

Note: A collation descriptor (COLDE) can only be specified in the format buffer of the L9<br />

comm<strong>and</strong> <strong>and</strong> only when the decode option has been specified in the user exit. The value<br />

returned is not the index value but the original field value.<br />

Subcode Meaning<br />

1<br />

2<br />

3<br />

4<br />

5<br />

Spacing element nX with n=0 or n>255 not allowed.<br />

An invalid sequence of format buffer elements was specified.<br />

Miscellaneous types of specification errors were found in the format buffer.<br />

A field name was undefined or not elementary.<br />

Format without fields.<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 />

71

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

Saved successfully!

Ooh no, something went wrong!