Timeout problems

Timeout problems in an E2E automation environment may occur if you access the data of a remote SA z/OS domain or remote SA z/OS resources.

The data that is displayed has to be requested from the automation adapter. These end-to-end automation requests are mapped to SA z/OS commands that query the requested data from the automation manager. Before sending the query commands to the automation manager, the primary automation agent checks the expiration time for the end-to-end automation requests. If the expiration time that remains is too short, the requested command is rejected, resulting in error message ING249E that indicates that a task execution request timed out.

The expiration time of an end-to-end automation request is determined by where it is issued, as follows:

Request issued from:	Expiration time determined by:
SMU Server	The timeout interval that is defined in the WebSphere® Admin Console for the environment variable com.ibm.eez.aab.invocation-timeout-seconds
The automation adapter (such as INIT_DOMAIN)	The timeout interval that is defined in the automation adapter ing.adapter.plugin.properties configuration file
E2E agent	The timeout interval INGAGT_CON_TIMEOUT that is defined in the automation agent inge2eagt.properties configuration file

It is possible that an end-to-end automation request that has been issued might be queued in the automation adapter or the NetView operator task for a certain period of time. You should therefore make the timeout interval large enough to take this delay into account.

For details about the relationship between the expiration time and the WAIT parameter of SA z/OS commands, see The WAIT Parameter.