
	Version 9.5 SP1	SEARCH CONTENTS \| PDF BOOKS \| HOME UP PREV NEXT

— Error Messages and Codes —

Message Class 2010 - EntireX WebSphere MQ RPC Server

This section describes error messages which can occur in the WebSphere MQ RPC Server. The messages have the format:

2010nnnn

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

Overview of Messages

20100001 | 20100009 | 20100010 | 20100011 | 20100012 | 20100013 | 20100015 | 20100022 | 20100202 | 20100203 | 20100204 | 20100205 | 20100206 | 20100207 | 20100208 | 20100209 | 20100210 | 20100211 | 20100212 | 20100213 | 20100214 | 20100215 | 20100216 | 20100217 | 20100218

20100001	Process request and reply: invalid action <number indicating action>
Explanation	While processing the request and the reply, an action was to take place which is illegal in the current state.
Action	Contact Software AG support.

20100009	<Exception with detailed message >
Explanation	An exception occurred while formatting the message. In most cases, the reason is an inconsistency in the metadata.
Action	See detailed message or contact Software AG support.

20100010	Compression=off not possible
Explanation	An RPC with compression 0 is not supported.
Action	Change compression to 1 or 2.

20100011 Type of marshalling not allowed
or
Unsupported call type <number of call type>

Explanation

There are two reasons for this error code.

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.
The RPC call type is wrong.

Action

Check configuration and client.

20100012	<Exception with detailed message>
Explanation	This exception occurs in message processing.
Action	See detailed message and contact Software AG support.

20100013

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.

Marshalling of message failed before sending to CICS ECI.
The received message has not the expected layout and the values cannot be unmarshalled from it.

Action

Check metadata (IDL, SVM, adapter connections) for consistency or contact Software AG support.

20100015	Transformation error on request: <Exception with detailed message>
Explanation	This exception occurs in message processing.
Action	See detailed message or contact Software AG support.

20100022

Unsupported command <command>
or
Exception: <Exception with detailed message>

Explanation

There are two reasons for this error code.

An unknown internal command is used.
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.

20100202	Exception with detailed message
Explanation	An exception occurred when sending a message to MQ.
Action	See error code and description and follow detailed message.

20100203	Exception with detailed message
Explanation	An exception occurred when doing a commit of an MQ session.
Action	See error code and description and follow detailed message.

20100204	Exception with detailed message
Explanation	An exception occurred when doing a backout of an MQ session.
Action	See error code and description and follow detailed message.

20100205	Exception with detailed message
Explanation	An exception occurred during shutdown processing.
Action	See error code and description and follow detailed message.

20100206	Exception with detailed message
Explanation	An exception occurred when receiving a message from MQ.
Action	See error code and description and follow detailed message.

20100207	Exception with detailed message
Explanation	An exception occurred when opening an MQ queue.
Action	See error code and description and follow detailed message.

20100208	Exception with detailed message
Explanation	An exception occurred when connecting to an MQ queue manager.
Action	See error code and description and follow detailed message.

20100209	No input queue opened
Explanation	Receive failed because no input queue was opened.
Action	Specify an input queue in the configuration file.

20100210	No output queue opened
Explanation	Send failed because no output queue was opened.
Action	Define an output queue in the configuration file.

20100211	Neither an input nor an output queue opened
Explanation	WebSphere MQ RPC Server cannot start because neither an input nor an output queue was opened.
Action	Specify an input and/or output queue in the configuration file.

20100212	Input queue identical to reply queue
Explanation	Request reply can only be done if the input queue and the output (reply) queue are different.
Action	Specify an input and output queue with different names in the configuration file

20100213	Exception with detailed message
Explanation	An exception occurred when calling the `beforePut` method in the user exit class.
Action	See error description and follow detailed message.

20100214	Exception with detailed message
Explanation	An exception occurred when calling the `beforeGetmethod` in the user exit class.
Action	See error description and follow detailed message.

20100215	Exception with detailed message
Explanation	An exception occurred when calling the `afterGetmethod` in the user exit class.
Action	See error description and follow detailed message.

20100216	Cannot load user exit class
Explanation	An exception occurred when loading or creating the user exit class.
Action	See error description and follow detailed message.

20100217	Start of WebSphere MQ Listener failed
Explanation	An exception occurred when starting the WebSphere MQ Listener.
Action	See error description and follow detailed message.

20100218	Field MQEnvironment... error
Explanation	An error occurred when accessing one of the `entirex.wmqbridge.environment` properties.
Action	See error description and follow detailed message.

SEARCH CONTENTS | PDF BOOKS | HOME UP PREV NEXT