Message Class 0079 - EntireX ACI - Error in Broker Stub

This is a problem with the Broker stub used by the application. The stub did not send the Broker call in the correct internal format.

Ensure that the correct version of the Broker stub is being used. Check the log data set for an image of the internal format. Examine this string for the user issuing the call.

An invalid value is provided in the ACI field :1:.

Correct the value supplied in ACI field :1:.

The size of ACI field :1: is out of range. This might indicate a transport problem.

Check the value supplied in ACI field :1:. Contact Software AG support if needed.

An internal protocol error has occurred between ACI and EntireX Broker or transmission has been corrupted.

Contact Software AG support.

An internal protocol error has occurred between ACI and EntireX Broker or transmission has been corrupted.

Contact Software AG support.

The mainframe Assembler stub supports only Natural Version 4 and above.

Use Natural Version 4 or above.

This is a problem with the Broker stub used by the application. The stub has not sent the EntireX Broker call in the correct internal format.

Ensure that the version of the Broker stub being used matches the version of the Broker you are accessing. Check the log data set for an image of the internal format. Examine this string for the user issuing the call.

An internal inconsistency in the response from the EntireX Broker has been detected: the size of the received data is greater than the return length, that is, the length of the data returned from the application.

Contact Software AG support.

The stub received a reply that indicates an invalid sender. The received data is rejected.

The BROKER-ID is probably invalid. The addressee does not support the communication protocol of the Broker.

This is a problem with the Broker stub used by the application. The stub did not send the EntireX Broker call in the correct internal format.

Ensure that the Broker stub being used is the correct one. Check the log data set for an image of the internal format. Examine this string for the user issuing the call.

This is a problem with the Broker stub used by the application. The stub did not send the EntireX Broker call in the correct internal format.

Check that the Broker stub being used is the correct one. Check the log data set for an image of the internal format. Examine this string for the user issuing the call.

This is a problem with the Broker stub used by the application. The stub did not send the EntireX Broker call in the correct internal format.

Check that the Broker stub being used is the correct one. Check the log data set for an image of the internal format. Examine this string for the user issuing the call.

The Broker returned an invalid internal format to the caller. The length of the returned string is not positive.

Contact Software AG support.

The EntireX Broker stub cannot allocate the storage needed as a work area.

If you are using a Natural application in a mainframe environment, try to reduce or remove Natural buffers from the Natural space management. Please refer to the appropriate Natural Operations documentation for valid Natural buffer profile parameters such as ASIZE, CSIZE, DSIZE. When issuing the first call from any mainframe Natural platform, a buffer of 33K must be available within Natural space management.

Under CICS, the broker stub received a CICS error=RESP/RESP2 while calling the CICS routine pgm_name (normally ADACICS).

Check the CICS documentation for the meaning of the response codes.

The reply string could not be generated due to an internal buffer overflow.

Contact Software AG support.

The Broker kernel has received a command string that contains unknown binary field extensions.

Contact Software AG support.

The message from EntireX Broker does not contain the necessary protocol information.

Contact Software AG support.

EntireX Broker received a request with invalid binary protocol parts.

Contact Software AG support.

An application has attempted to call EntireX Broker multiple times simultaneously, either from two different threads or from an asynchronous signal routine.

Avoid calling the Broker stub multiple times. A thread-safe version may be available with one of the next EntireX Broker versions.

The components (e.g. OpenSSL libraries for SSL transport) are not fully available. Therefore, the desired transport in the Broker stub cannot be initialized. Under z/OS, the most likely causes of this are:

1. The application is running on a version of z/OS below z/OS 1.6.

2. The Language Environment POSIX runtime option has the value OFF.

Use an alternative transport mechanism or make the missing components available.

Broker stub could not be loaded.

Please check environment variable ETBLNK. It should specify the full path name of the Broker stub.

The stub requires a higher z/OS version.

See z/OS Prerequisites for supported versions.

The BPX1SDD call to make subtasks processes failed.

See z/OS UNIX System Services Messages and Codes for a description of the return values.

Under BS2000 and z/VSE, the Adabas link routine is loaded dynamically. However, the stub was unable to load the Adabas link routine.

Assign the Adabas load library.

Under z/OS, the Adabas link routine is loaded dynamically. However, the stub was unable to load the Adabas link routine.

Assign the Adabas load library to the STEPLIB chain.

The stub BROKER cannot load module BROKER2.

Add the EXX load library with module BROKER2 to the STEPLIB chain and rerun the application.