Message Class 2010 - EntireX WebSphere MQ RPC Server

While processing the request and the reply, an action was to take place which is illegal in the current state.

Contact Software AG support.

An exception occurred while formatting the message. In most cases, the reason is an inconsistency in the metadata.

See detailed message or contact Software AG support.

An RPC with compression 0 is not supported.

Change compression to 1 or 2.

There are two reasons for this error code.

1. For the marshalling property, the values 'cobol', 'natural', and '' are allowed. Reason: The value of the property may be invalid. Or: The RPC from the client is in the wrong marshalling.

2. The RPC call type is wrong.

Check configuration and client.

This exception occurs in message processing.

See detailed message and contact Software AG support.

There are two reasons for this error code.

1. Marshalling of message failed before sending to CICS ECI.

2. The received message does not have the expected layout and the values cannot be unmarshalled from it.

Check the following metadata for consistency or contact Software AG support:

• IDL file, see Software AG IDL File.

• Server mapping file. A server mapping file is an EntireX Workbench file with extension .svm or .cvm. See Server Mapping Files for COBOL.

• Adapter connections.

This exception occurs in message processing.

See detailed message or contact Software AG support.

There are two reasons for this error code.

1. An unknown internal command is used.

2. An exception occurred during action processing. The log files contain a stack trace.

See detailed message and log files or contact Software AG support.

An exception occurred when sending a message to MQ.

See error code and description and follow detailed message.

An exception occurred when doing a commit of an MQ session.

See error code and description and follow detailed message.

An exception occurred when doing a backout of an MQ session.

See error code and description and follow detailed message.

An exception occurred during shutdown processing.

See error code and description and follow detailed message.

An exception occurred when receiving a message from MQ.

See error code and description and follow detailed message.

An exception occurred when opening an MQ queue.

See error code and description and follow detailed message.

An exception occurred when connecting to an MQ queue manager.

See error code and description and follow detailed message.

Receive failed because no input queue was opened.

Specify an input queue in the configuration file.

Send failed because no output queue was opened.

Define an output queue in the configuration file.

WebSphere MQ RPC Server cannot start because neither an input nor an output queue was opened.

Specify an input and/or output queue in the configuration file.

Request reply can only be done if the input queue and the output (reply) queue are different.

Specify an input and output queue with different names in the configuration file

An exception occurred when calling the beforePut method in the user exit class.

See error description and follow detailed message.

An exception occurred when calling the beforeGetmethod in the user exit class.

See error description and follow detailed message.

An exception occurred when calling the afterGetmethod in the user exit class.

See error description and follow detailed message.

An exception occurred when loading or creating the user exit class.

See error description and follow detailed message.

An exception occurred when starting the WebSphere MQ Listener.

See error description and follow detailed message.

An error occurred when accessing one of the entirex.wmqbridge.environment properties.

See error description and follow detailed message.