Message Class 2011 - Connections to IMS Connect

This section describes messages that can occur with connections from the webMethods EntireX Adapter for Integration Server to IMS Connect. The messages have the format:

2011nnnn

where 2011 is the message class, and
nnnn is the message number in the range 0000 - 9999

Overview of Messages

20110001 | 20110009 | 20110010 | 20110012 | 20110013 | 20110014 | 20110015 | 20110022 | 20110023 | 20110301 | 20110302 | 20110303 | 20110304
20110001 Process request and reply: illegal action <number indicating action>
Explanation

During request/reply processing the next action is illegal in the current state.

Action

Contact Software AG Support.
20110009 <Exception with detailed message >
Explanation

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

Action

See detailed message or contact Software AG Support.
20110010 Compression=off not possible
Explanation

An RPC with compression "0" or "off" is not supported.

Action

Change compression to 1 or 2.
20110012 <Exception with detailed message>
Explanation

This exception occurs in message processing.
Action

See detailed message and contact Software AG Support.
20110013 Preparing message failed, see log for details
or
Message received from server does not fit buffer
Explanation

There are two reasons for this error code.

  1. Marshalling of message failed before sending to IMS Connect.

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

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

Details can be found in wmentirex.log with trace level 2.
20110014 Transformation error on reply: <Exception with detailed message>
Explanation

The metadata is inconsistent or this data type is not supported.
Action

See detailed message or contact Software AG Support.
20110015 Transformation error on request: <Exception with detailed message>
Explanation

This data type is not supported.
Action

See detailed message or contact Software AG Support.
20110022 Unsupported command <command>.
or
Exception: <Exception with detailed message>
Explanation

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.
Action

See detailed message and log files or contact Software AG Support.
20110023 Preparing message failed, see log for details
Explanation

Marshalling of message failed before sending to IMS Connect.
Action

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

Details can be found in wmentirex.log with trace level 2.
20110301 Receive only not supported
Explanation

This type of call is not supported.
Action

Modify your client.
20110302 Send only not supported
Explanation

This type of call is not supported.
Action

Modify your client.
20110303 <detailed error message from IMS Connect>
Explanation

IMS Connect reported an error, or the configuration is wrong.

If IMS Connect returns code 16 and reason code 64, one cause is that the IMS exit is not installed or is not running. The default exit name is HWSSMPL0 (old) or HWSSMPL1 (new). Other configurations may also result in this return code and reason code.

If the IMS Connect connection in the EntireX Adapter uses a port which is not related to IMS but to some other application, a call may result in the following message: Unable to invoke adapter service <service name> [ADA.800.500] WmEntireX: exception while executing service: 2011 0303 java.io.EOFException

If the RPC Server for IMS Connect uses a port which is not related to IMS but to some other application, a call may result in the following message: exception while executing service: 2011 0303 java.io.EOFException
Action

Use the error code from IMS Connect to correct this or correct the configuration.

20110304 Conversations not supported
Explanation

IMS Connect does not support conversational RPC calls.
Action

Use non-conversational calls.