A response timeout
occurs after the request has been forwarded to the CICS® server.
It can happen to a synchronous call, an asynchronous call, or to the
reply solicitation call that retrieves the reply from an asynchronous
call.
This can happen for the following reasons:
- The call was intended to be the only call of a new LUW. The LUW
was started, but the user application cannot determine whether updates
were performed, and whether they were committed or backed out.
- The call was intended to end an existing LUW. The LUW has ended,
but the user application cannot determine whether updates were performed,
and whether they were committed or backed out.
- The call was intended to continue or to end an existing LUW. The
LUW persists, and changes to recoverable resources are still pending.
When an IPIC connection to CICS is used, the ECI timeout value can be set
by the client application or configured for the IPIC connection in
the Gateway daemon. When an EXCI connection to CICS is used, the ECI timeout value is controlled
by the TIMEOUT parameter in the EXCI options table DFHXCOPT.