The messages have the format:
2016nnnn
where | 2016 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999 |
20160001 | 20160009 | 20160010 | 20160012 | 20160013 | 20160014 | 20160015 | 20160022 | 20160023 | 20160100 | 20160101 | 20160102 | 20160103 | 20160104 | 20160105 | 20160106 | 20160107 | 20160108 | 20160109 | 20160110 | 20161000 | 20161001 | 20161003 | 20161004 | 20161005 | 20161007 | 20161008 | 20161009 | 20161010 | 20161013 | 20161014 | 20161015 | 20161016 | 20161017 | 20161018 | 20161019 | 20161020 | 20161021 | 20161022 | 20161023 | 20161101 | 20161102 | 20161103 | 20161104 | 20161105 | 20161106
20160001 | 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. |
20160009 | <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. |
20160010 | Compression=off not possible |
Explanation |
An RPC with compression "0" or "off" is not supported. |
Action |
Change compression to 1 or 2. |
20160012 | <Exception with detailed message> |
Explanation |
This exception occurs in message processing. |
Action |
See detailed message and contact Software AG support. |
20160013 | 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:
|
20160014 | 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. |
20160015 | Transformation error on request: <Exception with detailed message> |
Explanation |
This data type is not supported. |
Action |
See detailed message or contact Software AG support. |
20160022 | Unsupported command <command>. or Exception: <Exception with detailed message> |
Explanation |
There are two reasons for this error code.
|
Action |
See detailed message and log files or contact Software AG support. |
20160023 | Preparing message failed, see log for details |
Explanation |
Marshalling of message failed before sending to CICS. |
Action |
Check metadata (IDL, SVM, adapter connections) for consistency or contact Software AG support.
Details can be found in |
20160100 | Receive only not supported |
Explanation |
This type of call is not supported. |
Action |
Modify your client. |
20160101 | Invalid program name |
Explanation |
Program name exceeds the maximum of 8 bytes. |
Action |
Modify your client. |
20160102 | Reliable Send not supported |
Explanation |
This type of call is not supported. |
Action |
Modify your client. |
20160103 | Send only not supported |
Explanation |
This type of call is not supported. |
Action |
Modify your client. |
20160104 | Invalid encoding <message> |
Explanation |
The configured encoding is not valid. |
Action |
Modify your configuration. |
20160105 | <detailed error message from the socket layer> |
Explanation |
Communication to the CICS Socket Listener resulted in an error. See the error message for details. |
Action |
Use the error message from the socket layer to correct this or correct the configuration. |
20160106 | Create PassTicket error: <error message> |
Explanation |
Creation of the PassTicket was not possible. Check the error message for details. Typically one of the input parameters (user ID, application name, or secured signon key) is not valid. |
Action |
Modify the configuration. |
20160107 | Invalid eyecatcher <message> |
Explanation |
The response returned from CICS does not contain the expected eyecatcher. Possible reasons include:
|
Action |
Modify the configuration. |
20160108 | Invalid response length |
Explanation |
The reply is shorter than the minimum length. |
Action |
Check the configuration (see 20160107) or contact Software AG support. |
20160109 | Not enough memory for response |
Explanation |
The Java virtual machine does not provide enough memory to process the response. |
Action |
Check the configuration (see 20160107) or increase the memory of the JVM. |
20160110 | Internal version mismatch, received %s, expected %d |
Explanation |
The response returned from CICS does not contain the expected version. |
Action |
Contact Software AG support. |
20161000 | RFE Version not supported |
Explanation |
The UNIX/Windows components and RPC RFE cannot agree to a valid protocol version. |
Action |
Verify if UNIX/Windows components and RPC RFE run with supported versions. |
20161001 | Memory allocation failed |
Explanation |
Cannot allocate memory in CICS region. |
Action |
Check CICS log for previous errors and for CICS short-on-storage conditions. |
20161003 | Cannot take socket connection |
Explanation |
Error from CICS TCP layer. |
Action |
Check for TCP-related errors in CICS log or contact Software AG support. |
20161004 | Cannot create Socket |
Explanation |
Error from CICS TCP layer. |
Action |
Check for TCP-related errors in CICS log or contact Software AG support. |
20161005 | Cannot bind Socket |
Explanation |
Error from CICS TCP layer. |
Action |
Check for TCP-related errors in CICS log or contact Software AG support. |
20161007 | Select Socket failed |
Explanation |
Error from CICS TCP layer. |
Action |
Check for TCP-related errors in CICS log or contact Software AG support. |
20161008 | Communication timeout exceeded |
Explanation |
The timeout value configured on UNIX/Windows side has been exceeded. |
Action |
Check timeout value on UNIX/Windows side or contact Software AG support. |
20161009 | Recv Socket failed |
Explanation |
Error from CICS TCP layer. |
Action |
Check for TCP-related errors in CICS log or contact Software AG support. |
20161010 | Partner closed connection |
Explanation |
This is not an error. It indicates that the UNIX/Windows component closed the connections. |
Action |
None. |
20161013 | Invalid request data |
Explanation |
RPC RFE received data which does not apply to the expected protocol data. |
Action |
Configure trace level 3 on UNIX/Windows side to display the data in CICS log. |
20161014 | Internal: missing data in packet |
Explanation |
RPC RFE received data which does not apply to the expected protocol data. |
Action |
Contact Software AG support. |
20161015 | Unsupported interface type |
Explanation |
RPC RFE received data which does not apply to the expected protocol data. |
Action |
Contact Software AG support. |
20161016 | Unsupported request type |
Explanation |
RPC RFE received data which does not apply to the expected protocol data. |
Action |
Contact Software AG support. |
20161017 | Invalid data %s |
Explanation |
RPC RFE received data which does not apply to the expected protocol data.
|
Action |
Contact Software AG support. |
20161018 | EXEC CICS %s error, resp=%d resp2=%d |
Explanation |
Error from executing CICS command. |
Action |
Check CICS documentation for |
20161019 | Abend %.4s occurred in program %.8s psw=%s |
Explanation |
Abnormal end occurred. |
Action |
Check CICS log for a dump and contact Software AG support. |
20161020 | CICS VERIFY error: %.200s |
Explanation |
Error from executing CICS |
Action |
Check for conditions in dynamic message text or contact Software AG support. |
20161021 | Error from system function %s errno:%d errno2:0x%4.8X |
Explanation |
Error from z/OS system function. |
Action |
Check CICS log for extended error information ( |
20161022 | Invalid definition of user task %.4s: %s |
Explanation |
The user task defined in the EntireX Adapter/RPC Server is not correctly defined in CICS. |
Action |
Define the user task as CICS task with the program |
20161023 | Cannot give socket connection |
Explanation |
Error passing the socket to the defined user task. |
Action |
Run with trace (set in EntireX Adapter/RPC server). The trace output provides additional error information. See
|
20161101 | CICS program %s call error, resp=%d resp2=%d |
Explanation |
Error from executing CICS command |
Action |
Check CICS documentation for |
20161102 | CICS Syncpoint error, resp=%d resp2=%d |
Explanation |
Error from executing CICS command |
Action |
Check CICS documentation for |
20161103 | CICS Rollback error, resp=%d resp2=%d |
Explanation |
Error from executing CICS command |
Action |
Check CICS documentation for |
20161104 | CICS Put Container %s error, resp=%d resp2=%d |
Explanation |
Error from executing CICS command |
Action |
Check CICS documentation for |
20161105 | CICS Get Container %s error, resp=%d resp2=%d |
Explanation |
Error from executing CICS command |
Action |
Check CICS documentation for |
20161106 | CICS Call Container %s error, resp=%d resp2=%d |
Explanation |
Error from executing CICS command |
Action |
Check CICS documentation for |