
Administration	Version 5.9.1	SEARCH INDEX CONTENTS \| PDF PAGE PDF BOOKS \| HOME UP PREV NEXT

— Messages and Codes —

Entire Net-Work Codes

This document contains the following types of response codes:

Code Type	Description
Entire Net-Work Codes	A group of Adabas codes reserved for Entire Net-Work.
Adabas Response Codes	Adabas response codes that refer to problems with interregion communication in one way or another. In Entire Net-Work environments, the cause for these response codes is not always as apparent as in single systems. This is due to the fact that all calls are passed through interregion communications in two places: first they are passed from the user`s task to Entire Net-Work, then, on the server's node, they are passed from Entire Net-Work to the server. In both instances the same types of errors may occur. Therefore it is sometimes difficult, if not impossible, to guess on which node the problem was encountered. To aid in diagnosing such situations, Entire Net-Work provides the node ID (targetid) of the Entire Net-Work node where the problem was encountered for all problems related to the response codes listed in the following pages. The information is returned in the Additions-2 field of the Adabas control block (ACBADD2 in ADACB). Note that this field is not modified by Entire Net-Work under any other circumstances. In some cases, where the problem prevents the call from reaching Entire Net-Work on the user's node, the information obviously cannot be provided by Entire Net-Work.

Code Type

Description

A group of Adabas codes reserved for Entire Net-Work.

Adabas Response Codes

Adabas response codes that refer to problems with interregion communication in one way or another.

In Entire Net-Work environments, the cause for these response codes is not always as apparent as in single systems. This is due to the fact that all calls are passed through interregion communications in two places: first they are passed from the user`s task to Entire Net-Work, then, on the server's node, they are passed from Entire Net-Work to the server. In both instances the same types of errors may occur. Therefore it is sometimes difficult, if not impossible, to guess on which node the problem was encountered.

To aid in diagnosing such situations, Entire Net-Work provides the node ID (targetid) of the Entire Net-Work node where the problem was encountered for all problems related to the response codes listed in the following pages. The information is returned in the Additions-2 field of the Adabas control block (ACBADD2 in ADACB). Note that this field is not modified by Entire Net-Work under any other circumstances. In some cases, where the problem prevents the call from reaching Entire Net-Work on the user's node, the information obviously cannot be provided by Entire Net-Work.

The codes are described in alphanumeric order.

RESPONSE 148

Explanation

The Adabas nucleus was either not active or not accessible. Refer to the hexadecimal subcode that appears in the the Adabas Control Block's Additions 2 field, the low-order (rightmost) two bytes. The following are the decimal equivalents of those subcodes and their meanings:

Note:
If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field may also contain the ID of the Entire Net-Work node that issued this response code.

1	Exclusive database control requirement conflicts with read-only nucleus status.
2	A nonprivileged call was made to the nucleus while it was in utility-only (UTI) mode.
3	The nucleus is performing an ADAEND operation, and either a new user is attempting to begin operation or an existing user in ET status is trying to continue operation.

Code Type

Adabas response code

RESPONSE 151
Explanation	A command queue overflow occurred.
Code Type	Adabas response code
Action	The DBA may increase the value for the NC parameter and/or the command may be issued when a lower level of command activity is in effect. If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.

RESPONSE 210

Explanation

Logical ID greater than 255 (internal error).

If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.

Code Type

Adabas response code

RESPONSE 211

Explanation

Invalid ID table index in UB (internal error).

If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.

Code Type

Adabas response code

RESPONSE 213
Explanation	ID table not found (SVC not properly installed). If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.
Code Type	Adabas response code
Action	Inform the DBA. Adabas installation procedure not properly executed.

RESPONSE 216

Explanation

Command rejected by user exit.

If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.

Code Type

Adabas response code

RESPONSE 217

Explanation

Command rejected by user exit.

If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.

Code Type

Adabas response code

RESPONSE 220
Explanation	Buffer shortage: the request was rejected by Entire Net-Work due to a shortage of short term buffers. The ACBADD2 field in the Adabas control block contains the nodeid of the node in error in the leftmost 2 bytes.
Code Type	Entire Net-Work response code
Action	Increase the size of the short term buffer allocated on the BUFFER= parameter of the NODE statement.

RESPONSE 221
Explanation	The LU size of the remote partner is smaller than the size required for the Adabas request.
Code Type	Entire Net-Work response code
Action	Either increase the size specified for the LU= parameter on the remote system, or modify the application to reduce its buffer sizes.

RESPONSE 222 - 223 (reserved)

RESPONSE 224
Explanation	Reply timeout: the request waited for a reply for a longer time period than specified by the REPLYTIM parameter in either the NODE statement or the SET operator command. The reply may be delayed or lost due to a target malfunction, or because of a connecting link failure. If you are using Natural, and all connections are verified, check the ADAMODE setting. The ADAMODE=0 setting is the only option Entire Net-Work supports.
Code Type	Entire Net-Work response code

RESPONSE 225 - 227 (reserved)

RESPONSE 228
Explanation	ADALCO is UES-enabled, but one of the following problems exists: The SVC is not UES-enabled (the subcode in additions 2 is X'01') or the target database is not UES-enabled (the subcode in additions 2 is X'02').
Code Type	Entire Net-Work response code
Action	Make sure Adabas and the SVC are at the V712 level, and that the database is UES-enabled.

RESPONSE 229
Explanation	Translation error: the Entire Net-Work 5 convertor detected an inconsistency and/or error in the application format buffer or search buffer, and is unable to correctly translate the user's data.
Code Type	Entire Net-Work response code

RESPONSE 252

Explanation

An error occurred during Adabas SVC processing (post error).

If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.

Code Type

Adabas response code

RESPONSE 253

Explanation

An error occurred during Adabas SVC processing (invalid buffer length detected).

If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.

Code Type

Adabas response code

RESPONSE 254

Explanation

One of the following has occurred:

An internal error occurred during processing of an attached buffer (buffer overflow)
The CT parameter limit was exceeded. Message ADAM93 (or a similar message) is printed or displayed on the console.

If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.

Code Type

Adabas response code

RESPONSE 255

Explanation

All attached buffers were allocated at the time the command was processed. Buffer allocation (NAB) high water marks" may not reflect this condition when no buffer allocation occurs.

If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (Adabas Control Block) contain the ID of the Entire Net-Work node that issued this response code.

Code Type

Adabas response code

SEARCH INDEX CONTENTS | PDF PAGE PDF BOOKS | HOME UP PREV NEXT