IMS TM resource adapter timeouts

There are several configurable timeouts that can be used to prevent applications from hanging due to failures during execution of an interaction.

On occasion, network problems affect the transmission of data between a client and IMS™. Without a way to handle such unexpected problems, applications can "hang." An example of such an occurrence would be the failure of a router on the TCP/IP path between the IMS TM resource adapter and IMS Connect. There are several timeouts that may play a part in recovering from such a failure. IMS TM resource adapter is directly involved with two of them. The Execution Timeout property of IMSInteractionSpec is used to deal with problems between IMS Connect and IMS such as a failure of their XCF communications link or a failure in IMS which leads to the target transaction not running or its output not being returned to IMS Connect. The Socket Timeout property of IMSInteractionSpec is used to address problems affecting TCP/IP communication between the IMS TM resource adapter and IMS Connect. This section will discuss these two configurable timeout options as well as other timeouts which could affect an interaction.

You can configure the execution timeout and socket timeout properties of IMSInteractionSpec to handle problems that occur during execution of an interaction.

The timer for Execution Timeout runs inside the Socket Timeout window; therefore, the Socket Timeout property should always be set to a value that is larger than the Execution Timeout value.

In addition, there are other timeouts which may affect the way errors are handled.


Feedback