This message class contains messages that can occur with connections to CICS ECI. The messages have the format:
2012nnnn
where | 2012 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999 |
20120001 | 20120009 | 20120010 | 20120012 | 20120013 | 20120014 | 20120015 | 20120022 | 20120023 | 20120351 | 20120352 | 20120353 | 20120354
20120001 | 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. |
20120009 | <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. |
20120010 | Compression=off not possible. |
Explanation |
An RPC with compression "0" ("off") is not supported. |
Action |
Change compression to 1 or 2. |
20120012 | <Exception with detailed message> |
Explanation |
This exception occurs in message processing. |
Action |
See detailed message and contact Software AG support. |
20120013 | 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.
|
Action |
Check the following metadata for consistency or contact Software AG support:
|
20120014 | 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. |
20120015 | Transformation error on request: <Exception with detailed message>. |
Explanation |
This data type is not supported. |
Action |
See detailed message or Contact Software AG support. |
20120022 | 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. |
20120023 | Preparing message failed, see log for details |
Explanation |
Marshalling of message failed before sending to CICS ECI. |
Action |
Check metadata (IDL, SVM, adapter connections) for consistency or contact Software AG support.
Details can be found in |
20120351 | Receive only not supported |
Explanation |
This type of call is not supported. |
Action |
Modify your client. |
20120352 | Send only not supported |
Explanation |
This type of call is not supported. |
Action |
Modify your client. |
20120353 | <detailed error message from CICS ECI> |
Explanation |
CICS ECI reported an error, or the configuration is wrong. This error number is also issued if the connection to CICS ECI is lost. |
Action |
Use the error code from CICS to correct this. The CICS error codes are described in the documentation of CICS from IBM. Possible error codes are (others may occur):
A call to CICS ECI can result in an EOF exception because of
|
20120354 | Conversations not supported |
Explanation |
CICS ECI does not support conversational RPC calls. |
Action |
Use non-conversational calls. |