The messages have the format:
2015nnnn
where | 2015 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999 |
20150001 | 20150009 | 20150010 | 20150012 | 20150013 | 20150014 | 20150015 | 20150022 | 20150023 | 20150050 | 20150051 | 20150100 | 20150101 | 20150102
20150001 | 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. |
20150009 | <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. |
20150010 | Compression=off not possible. |
Explanation |
An RPC with compression "0" ("off") is not supported. |
Action |
Change compression to 1 or 2. |
20150012 | <Exception with detailed message> |
Explanation |
This exception occurs in message processing. |
Action |
See detailed message and contact Software AG support. |
20150013 | 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:
|
20150014 | 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. |
20150015 | Transformation error on request: <Exception with detailed message>. |
Explanation |
This data type is not supported. |
Action |
See detailed message or Contact Software AG support. |
20150022 | 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. |
20150023 | Preparing message failed, see log for details |
Explanation |
Marshalling of message failed before sending to AS/400. |
Action |
Check metadata (IDL, SVM, adapter connections) for consistency or contact Software AG support.
Details can be found in |
20150050 | <detailed error message from AS/400> |
Explanation |
The AS/400 system reported an error. |
Action |
Use the error message from the AS/400 system to correct this. |
20150051 | <Exception with detailed message> |
Explanation |
This exception occurs when calling the AS/400 system. |
Action |
Use the exception message to correct this.. |
20150100 | Receive only not supported |
Explanation |
This type of call is not supported. |
Action |
Modify your client. |
20150101 | Conversations not supported |
Explanation |
AS/400 does not support conversational RPC calls. |
Action |
Use non-conversational calls. |
20150102 | Reliable send not supported |
Explanation |
This type of call is not supported. |
Action |
Modify your client. |