Message Class 0215 - EntireX ACI - Connection Error

The request received by Broker does not contain the required transport data. It may be caused by requests not intended for Broker.

The request is rejected.

There is no entry available to process the received user request. This message is issued if the maximum number of work queue elements is reached (see value of NUM-WQE attribute).

Increase the value of parameter NUM-WQE.

Communication pool is too small.

Increase size of the communication buffer (NUM-COMBUF) and retry.

The requested Broker specified in BROKER-ID is not reachable.

Check the BROKER-ID. If it is correct, check if ETB_TRANSPORT environment variable is defined and if defined, it should point to the desired transport method. If problem persists, contact your network administrator.

The broker stub was unable to initialize the environment.

The error text describes the problem situation. The necessary action depends on the actual problem description.

Adabas command queue overflow.

Increase the size of the NCQE parameter.

IUBL is too low and must be increased. Due to the increase of IUBL, it may be necessary to increase NABS, too.

Note:
In other environments, IUBL is also known as LU Size or TRANSFER_UNIT Size.

Increase IUBL.

The same as the Adabas 254 response code. The Adabas documentation states:

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 were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

Note:
The Adabas CT parameter corresponds to the EntireX startup parameter TIME.

Consider increasing the EntireX TIME parameter, or otherwise increase resources.

The same as the Adabas 255 response code. The Adabas documentation states:

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 were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

Settings for Broker attribute NUM-COMBUF possibly too low. See NUM-COMBUF under Broker Attributes.

Consider increasing the value of NUM-COMBUF. If the problem persists, contact Software AG support.

Connection error. A timeout occurred, based on the value specified in the TRANSPORT-TIMEOUT environment variable (ETB_TIMEOUT) and/or any client-specified wait time. Refer to that variable for more information.

Identify the cause of the timeout and correct it. If the problem remains, contact Software AG support.

ACI function FCT_SETSSLPARMS was not set, The necessary SSL parameters were not issued, and an SSL connection to the Broker was requested.

Issue missing ACI function FCT_SETSSLPARMS, or change the BROKER-ID to not use SSL.

The DN field in the SSL certificate supplied by the broker kernel does not match the hostname part of the broker ID.

Ensure that the broker kernel is configured to use the correct SSL certificate.

There is no entry available to process the received user request. This message is issued if the maximum number of work queue elements is reached (see value of NUM-WQE attribute).

Increase the value of parameter NUM-WQE.

Connection error. Broker command prefix length is invalid (internal error).

Contact Software AG support.

Connection error. Broker command API offset is invalid (internal error).

Contact Software AG support.

ADALNK or ADAUSER is not linked to the Broker stub. The stub cannot perform the transport call to the Broker kernel.

Link ADAUSER to the stub. See BROKER.

An internal error occurred while receiving an API request.

Contact Software AG support.

One of the WebSphere MQ modules could not be found.

Put MQ libraries in the Broker Services steplib or link library.

A local program has committed an error. The error text field contains specific error information.

Check the program and correct the error.

A remote program has committed an error. The error-text field contains specific error information.

Check the program and correct the error.

A Remote Attach DEREGISTER request has been issued, but either the TPNAME specified in the SERVICE field was not previously registered, or a DEREGISTER was issued with a blank TPNAME and the Remote Attach Manager currently has no TPNAMEs registered.

None.