Message Class 2017 - Connections to CICS IPIC

This message class contains messages that can occur with connections to CICS IPIC. The messages have the format:

2017nnnn

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

Overview of Messages

20170001 | 20170009 | 20170010 | 20170012 | 20170013 | 20170014 | 20170015 | 20170022 | 20170023 | 20170351 | 20170352 | 20170353 | 20170354
20170001 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.
20170009 <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.
20170010 Compression=off not possible.
Explanation

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

Change compression to 1 or 2.
20170012 <Exception with detailed message>
Explanation

This exception occurs in message processing.
Action

See detailed message and contact Software AG Support.
20170013 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 CICS IPIC.

  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:

Details can be found in wmentirex.log with trace level 2.
20170014 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.
20170015 Transformation error on request: <Exception with detailed message>.
Explanation

This data type is not supported.
Action

See detailed message or Contact Software AG Support.
20170022 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.
20170023 Preparing message failed, see log for details
Explanation

Marshalling of message failed before sending to CICS IPIC.
Action

Check the following metadata for consistency or contact Software AG Support:

Details can be found in wmentirex.log with trace level 2.
20170351 Receive only not supported
Explanation

This type of call is not supported.
Action

Modify your client.
20170352 Send only not supported
Explanation

This type of call is not supported.
Action

Modify your client.
20170353 <detailed error message from CICS IPIC>
Explanation

CICS IPIC reported an error, or the configuration is wrong. This error number is also issued if the connection to CICS IPIC 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):

  • AEI0: PGMIDERR
    possible reasons: Callee not found - the called program cannot be loaded by CICS. Check if the program is available in CICS RPL chain and installed in CICS.

  • ASRA
    possible reasons: Division by zero.

  • 4038: Index overwrite

  • TCII (CICS Abend)

A call to CICS IPIC can result in an EOF exception because of

  • Connection to the wrong port. There is some service listening on the port, but not CICS IPIC.

  • CICS IPIC is not correctly configured.
20170354 Conversations not supported
Explanation

CICS IPIC does not support conversational RPC calls.
Action

Use non-conversational calls.