Message Class 0078 - EntireX ACI - Error from Broker

EntireX Broker has tried to return an error number that it cannot find in the table of known messages.

Contact Software AG support.

The translation routine cannot be loaded (in RECEIVE function) because the translation routine control block was not created correctly when the service was registered.

Contact Software AG support.

Broker could not get enough memory during initialization.

Reduce the resource requirements in the attribute file OR increase the memory available to your broker job, if possible.

EntireX Broker detected an error during release of storage.

Contact Software AG support.

A server issued a DEREGISTER call with option QUIESCE while a user was still active (conversations were active), and a REGISTER call was issued. In this situation, EntireX Broker detected an error.

Contact Software AG support.

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 correct version of the EntireX 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.

The internal communication of Broker failed due to an operating system error.

Contact Software AG support.

Resources obtained for a Command and Infor Services query cannot released.

Contact Software AG support.

Currently, PSTORE is disconnected. Any active operation involving PSTORE is currently prohibited. This situation can occur when the Broker administrator has issued the CIS command DISCONNECT-PSTORE.

It may take some time before PSTORE will be connected again. Be careful not to have a loop programmed in this situation. Retry the call to EntireX Broker after the Broker administrator has issued the command CONNECT-PSTORE.

EntireX Broker has detected an internal inconsistency during info or command processing. The internal field length description is corrupted.

Contact Software AG support.

EntireX Broker has detected an error while searching for a free SCB extension entry. There is no SCB extension entry available.

This error should not occur with DYNAMIC-MEMORY-MANAGEMENT set to "YES" unless the maximum amount of memory has already been reached.

With DYNAMIC-MEMORY-MANAGEMENT set to "NO", the broker-specific attribute NUM-SERVICE-EXTENSION can be used to increase the number of service extension control blocks.

You may retrieve the allocated number of service extensions by using the program ETBINFO. Object ETB_INFO_RESOURCE_USAGE (CIS version 7 and above) returns all data about service extensions. See value of field nServiceExtensionEntriesAllocated.

EntireX Broker has detected an error while searching for a free TCB extension entry. There is no TCB extension available.

Contact Software AG support.

The Broker has detected an error while searching for a free TRE entry. There is no TRE entry available.

Contact Software AG support.

The Broker has detected an error while searching for the client SCB entry. There is no SCB entry for the client.

Contact Software AG support.

The Broker has detected an internal inconsistency during info or command processing. The internal description of the field type is corrupted.

Contact Software AG support.

Internal error during assembly of the Info return buffer.

Contact Software AG support.

EntireX Broker has detected an error in TOQ structures.

Contact Software AG support.

Internal error during inquiry of Info services.

Contact Software AG support.

The Broker has detected an error while searching for a free PCB entry. There is no PCB entry available.

Increase NUM-SERVER and/or NUM-CLIENT.

The Broker has detected an error while searching for a free PCB extension entry. There is no PCB extension entry available.

If you are not using dynamic memory management (Broker attribute DYNAMIC-MEMORY-MANAGEMENT), define an appropriate value for attribute NUM-PARTICIPANT-EXTENSION (NUM-SERVER * NUM-SERVICE + NUM-CLIENT).

EntireX Broker has detected an error while searching for a free topic control block. There is no TCB available.

Contact your Broker Administrator to increase the global attribute NUM-TOPIC.

The Broker has detected an error while searching for a free subscriber control block entry. There is no SUBSCB entry available

Contact Software AG support.

The Broker has detected an error while searching for a free SCB (Service Control Block) entry. There is no SCB entry available. The number of SCBs is set based upon the number of clients, servers, and services. When this error is returned, it means that all of the SCBs are in use. The current formula for the number of SCBs is:
NUM-CLIENTS + NUM-SERVERS + NUM-SERVICES + 5.

Recommendations:

• Increase NUM-SERVICE.

• Increase NUM-SERVER.

• Increase NUM-CLIENTS.

Increasing the values will increase the total number of SCBs.

To free up the idle SCBs sooner:

• Decrease CLIENT-NONACT.

• Decrease CONV-NONACT.

• Set SERVER-NONACT.

Decreasing the non-activity timers will cause the inactive resources to be made available to other users.

If DYNAMIC-MEMORY-MANAGEMENT is set to YES, this error should no longer occur.

An inconsistency occurred during the start of internal Info or Command Services.

Contact Software AG support.

The PSTORE operation to replace the contents of a unit of work failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An EntireX Broker function for a conversation with no units of work is requested, but the specified conversation contains units of work. The function is rejected.

Check the supplied conversation ID.

The Broker detected an error while searching for a free UWCB entry. No UWCB entry is available.

Contact Software AG support.

A client issued a SEND, RECEIVE, EOC, or SYNCPOINT call and the specified UOW does not exist.

This is a user error. Clients must ensure that the UOWs exist before any request is made.

A client issued a SYNCPOINT OPTION=COMMIT call specifying UOWID=BOTH and two UOWs in the correct status could not be found.

This is a user error. Clients must ensure that the UOWs to be operated on exist and are in the correct status.

A client issued a SEND, RECEIVE, EOC, or SYNCPOINT call and the specified UOW is not in the correct status for the requested operation.

This is a user error. Clients must ensure that the UOWs are in the correct status.

A client issued a SYNCPOINT call with OPTION=QUERY or OPTION=DELETE, and the specified UOW was not created by the caller of SYNCPOINT.

This is a user error. Only the creator of a UOW can QUERY or DELETE a UOW. Use the Command and Information Services to accomplish these operations on a UOW not created by the caller.

An error occurred while updating the persistent status of a UOW. The error is in the persistent store facility.

Examine the Broker log file to determine the type of error encountered. Contact Software AG support if necessary.

The store type specified with a SEND function is not the same as the store type specified with the first SEND for that UOW.

Do not change the store type after the first SEND for a UOW has been issued.

An attempt to write data to the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to read control data from the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to read message data from the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to update the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to write two data items to the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to delete data from the persistent store has failed.

Examine the Broker log file for more informatiofUOWIDn and contact Software AG support if necessary.

An attempt to scan for selected data on the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

Two UOWs with the same ID, on the same conversation, were encountered during restart. The Broker will not initialize.

It will be necessary to delete one or both of the UOWs before restarting. Contact Software AG support if necessary.

An encryption or decryption security exit attempted to change the size of a message.

Correct the user exit so that message sizes are not changed.

A request has specified a unit of work (UOW) operation. But because the broker-specific attribute MAX-UOWS is set to 0 (zero), unit of work operations are not allowed. See MAX-UOWS.

Ensure that the request is directed to the correct Broker and that the Broker supports UOWs.

A UOWID is required for a SYNCPOINT function that specifies a COMMIT, BACKOUT, or CANCEL option.

Provide a UOWID whenever you want to commit, back out, or cancel a UOW.

The message allocator is getting a request to obtain space for a message lower than or equal to zero. The request is rejected.

Contact Software AG support.

An error occurred while updating the receiver data of a UOW in the persistent store.

Examine the Broker log file to determine the type of error encountered. Contact Software AG support if necessary.

Broker keeps track of the sequence for sent and received non-persistent messages. The expected message number on receive does not match with the message number in the message queue control block. This indicates inconsistent data in the Broker memory pool. Broker will issue an error message and return this response code in the ACI.

Contact Software AG support.

The PSTORE operation to run a query is failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

The Broker could not allocate enough memory for a buffer into which the message to be character-converted should be copied.

As a short-term measure try reducing the number of worker tasks (NUM-WORKER in the Broker attribute file) since each worker task maintains a separate Translation buffer.

This message indicates a shortage of accounting control blocks.

Increase NUM-CONVERSATION.

A request for a UOW to be persisted (STORE=BROKER) cannot be accomplished, since at startup, the Broker attributes specify no persistent store (PSTORE=NO).

Review Broker attribute settings related to the persistent store.

A request for a UOW status to be persisted cannot be accomplished, since at startup, the Broker attributes specify no persistent store (PSTORE=NO).

Review Broker attribute settings related to the persistent store.

A publisher or a subscriber issued a call and the specified publication is not in the correct status for the requested operation.

This is a user error. Publishers and subscribers must ensure that the publications are in the correct status.

A publisher requested a publication which was not created by himself.

This is a user error. Only the creator of the publication can issue this request.

EntireX Broker tried to create an internal index for every unit of work. This operation failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

EntireX Broker tried to add an entry to the internal index for units of work. This operation failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

The logical read operation through the Adabas PSTORE returned an error.

Examine the Broker log file for more information and contact Software AG support if necessary.

EntireX Broker tried to delete an entry from the internal index for units of work. This operation failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

EntireX Broker tried to close the internal index for units of work. This operation failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

EntireX Broker has detected an error while searching for a free extensible topic Entry. There is no XTE available.

Contact your Broker Administrator to increase the global attribute NUM-TOPIC-TOTAL.

EntireX Broker has detected an error while searching for the publisher TCB entry. There is no TCB entry for the publisher.

Contact Software AG support.

Error occurs when Broker cannot access the subscriber store.

Please check Broker log for more detailed information.

Unable to set the persistent store-specific trace level.

Contact Software AG support.

An attempt to add a command log filter failed as there were no free command log filter entries.

Delete an existing command log filter or specify an increased value for the broker NUM-CMDLOG-FILTER attribute and restart the broker kernel.

Broker was started with WAIT-FOR-ACTIVE-PSTORE=YES but the persistent store is not active yet.

As soon as the persistent store is accessible, this temporary problem will no longer exist. Check that the assigned persistent store is in the process of starting.

EntireX Broker has detected an error while searching for a free proxy queue entry. There is no proxy queue entry available.

Contact Software AG support.

The maximum number of TCP/IP connections is derived from the number of available file descriptors. This maximum has been reached.

Increase the number of file descriptors.

The Broker is not available for user requests. The BROKER-ID used for the current request does not address a Broker with RUN-MODE=STANDARD.

Change the BROKER-ID to address a Broker with RUN-MODE=STANDARD.

EntireX Broker has detected an error while searching for a free node control block. There is no node control block available.

Contact Software AG support.

The proxy component of the requested communicator is not active and cannot be used to contact the partner Broker.

Check the output files for error messages issued by the communicator.

The internal communication path between the task ordering a pool allocation and the task executing the order received an error.

Broker log provides more detailed diagnostics about the reason not being able to perform post and wait between Broker threads.

There is an out of band request by the partner Broker to issue another handshake while the load procedure of the persistent store migration is already running.

Restart Load and Unload Broker to repeat the PSTORE migration.

A validation is performed by the Partner Brokers according to the Broker version number. This version information does not match.

Adjust the Broker environments so that the version of the Partner Brokers is the same.

A validation is performed by the Partner Brokers according to the Broker version number. This version information has not been sent by the partner.

Contact Software AG support.

A validation is performed by the Partner Brokers according to the platform architecture type. This type information does not match.

Adjust the Broker environments so that the partner Brokers are running on the same level and type of architecture.

A validation is performed by the Partner Brokers according to the platform architecture type. This type information has not been sent by the partner.

Contact Software AG support.

A validation is performed by the Partner Brokers according to the security setting. This security setting does not match.

Adjust the Broker environments so that the partner brokers are using the same security settings.

A validation is performed by the Partner Brokers according to the security setting. This security setting has not been sent by the partner.

Contact Software AG support.

The current request caused an abnormal exception in the Broker.

Contact your Administrator to send the diagnostic information of the Broker to Software AG support.

The Broker-to-Broker request has not finished yet. Broker is still waiting for the response of the partner Broker.

None.

User error loop was detected before and participant is currently not permitted to issue any Broker request.

Wait until participant is unlocked.

The Load Broker detected an inconsistency in the sent data. The expected end-of-data signature has not been sent.

Contact Software AG support.

UOW master record missing when reading UOW from Adabas PSTORE database. Indicates a corrupted or inconsistent Adabas PSTORE database.

Running with PSTORE=COLD and FORCE-COLD=YES fixes the problem by resetting the PSTORE database. Contact Software AG support if the recommended fix is not an option for your situation.

A call to the Adabas database returned an error response.

Check the Adabas response code for more details.

The unit of work in the c-tree PSTORE contains wrong data or an I/O error occurred.

Check if a wrong PSTORE-VERSION has been defined in the attribute file.

The space for the c-tree PSTORE is exhausted.

Move the PSTORE files to a location with more disk space and adjust the c-tree-specific PATH attribute accordingly.

The request to set the Adabas user ID was not successful.

Check the Adabas configuration.

This error indicates a data inconsistency.

Contact Software AG support.

An internal error occurred in the processing of the receive function.

Rerun Broker with TRACE-LEVEL=4. Contact Software AG support and provide the Broker log.

The runtime heap is too small. Broker was unable to allocate an RCB (Receive Control Block).

Change the runtime settings to increase the size of the runtime heap.