Automation domain remaining unavailable after error recovery

When restarting the automation manager or the INGPXDST communication task, during which the asynchronous communication path from the primary agent to the automation adapter is still available, the end-to-end automation manager is notified about the unavailable automation domain.

If there are problems notifying the end-to-end automation manager about the recovered error situation, the domain may remain unavailable rather than become available.

When creating the ready event for the end-to-end automation manager, requests sent to the automation manager may time out. In this case the ready event is not sent and the adapter online event is also not sent to the end-to-end automation manager.

By default, the primary agent waits 90 seconds for the response. A longer timeout interval can be provided in the common global variable INGREQ_WAIT.

The following error messages relating to these timeouts are written to the NETLOG:

ING008I INGPYAMC SERVICE FAILED, RC=2 - REASON=TIMEOUT MOD=INGRYEVT - GET_QUAL_RESOURCE_RELS (INGEVOBS)
ING235W No information from automation manager. READY event not  created for E2E.
ING276E Execution of a service timed out.

The command INGE2E RESYNC can also be used to notify the end-to-end automation manager about the recovered error situation.