Response timeout

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.

A response timeout can occur in the following situations:
  • The call was intended to be the only call of a new LUW. The LUW was started, but CICS Transaction Gateway 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 CICS Transaction Gateway 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.
Note: If you use timeouts in your applications, you must ensure that the application specifically confirms if resources were committed or backed out following a timeout.

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.