Other timeouts

In addition to execution and socket timeouts, other timeouts will impact your application's execution.

When developing your application, you must consider how other timeouts in addition to the IMS™ TM Resource Adapter Execution Timeout and Socket Timeout will impact your application's execution.

Timeouts overlap or even encapsulate one another. Such capability provides multiple layers of protection against problems that can cause your application to hang. This functionality should be considered when setting different timeouts: a longer timeout may mask a shorter timeout. For example, if the socket timeout is set to a lower value than the execution timeout, the socket timeout error will preclude an execution timeout and the absence of a response from IMS will remain unknown.

Other timeout values that may interact with the IMS TM resource adapter timeouts include the following values:

Consider one example of a timeout that will impact your application's execution: the interaction between applications on Websphere Application Server for z/OS® and the IMS TM resource adapter. The WebSphere® Application Server for z/OS consists of two parts: a controller and a set of one or more servants. By default, application work is timed, even when it is dispatched to a servant region. When an application dispatched to a servant region reaches its timeout, that servant region usually is abended and restarted. The server stays up and continues taking work. For this reason, you should use care when choosing execution timeout values that are greater than WebSphere Application Server timeout values, or when choosing the execution timeout value of -1 (which tells IMS Connect to wait indefinitely for a response from IMS).

Note: If you disable WebSphere Application Server timeouts, refer to the server documentation for information regarding additional timeout values that are not included with this documentation.

A second example of a timeout value that will impact your application's execution is the browser timeout. If the execution timeout value is configured to be greater than the browser timeout, then the execution timeout value is not used because the browser timeout occurs before the execution timeout.


Feedback