Message Class 2014 - COBOL Converter

The messages have the format:

2014nnnn

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

Overview of Messages

20140001 | 20140009 | 20140010 | 20140012 | 20140013 | 20140014 | 20140015 | 20140022 | 20140023 | 20140300 | 20140301 | 20140302

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


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


20140010 Compression=off not possible.
Explanation

An RPC with compression "0" ("off") is not supported.

Action

Change compression to 1 or 2.


20140012 <Exception with detailed message>
Explanation

This exception occurs in message processing.

Action

See detailed message and contact Software AG support.


20140013 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 COBOL Converter.

  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:


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


20140015 Transformation error on request: <Exception with detailed message>.
Explanation

This data type is not supported.

Action

See detailed message or Contact Software AG support.


20140022 Unsupported command <command>.
or
Exception: <Exception with detailed message>
Explanation

There are two reasons for this error code. First, an unknown internal command is used. Second, 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.


20140023 Preparing message failed, see log for details
Explanation

Marshalling of message failed before sending to COBOL Converter.

Action

Check metadata (IDL, SVM, adapter connections) for consistency or contact Software AG support. Details can be found in wmentirex.log with trace level 2.


20140300 Value for cobolInput misssing
Explanation

The service parameter cobolInput has either no value or an empty array assigned.

Action

Correct your application and assign a non-empty byte array object to the parameter cobolInput.


20140301 Value for cobolInput is not of type byte[]
Explanation

The service parameter cobolInput is not of type "byte array".

Action

Correct your application and assign a byte array object for the parameter cobolInput.


20140302 Conversations not supported
Explanation

COBOL Converter does not support conversational RPC.

Action

Use non-conversational calls.