Exit Recovery

An error in an XES exit that prevents the exit from completing actions required by XES or the application can impact not only the connected instance that suffers the error but all instances that are dependent on the completed actions. Two examples of this type of error in an XES exit are:

An event exit fails without providing a required event exit response. The sysplex-wide process that is dependent on that response hangs.
A contention/notify pair of exits fails without completely updating the CEPL or fields appropriate to processing the request. The results are unpredictable and could possibly lead to integrity exposures as well as sysplex-wide hang waiting for lock resources.

Because of the potential sysplex-wide impact of these errors, XES ends any connector's task that returns to XES abnormally with a non-retryable X'026' abend. The reason code from the abend indicates which of your exits suffered the error, and diagnostic information is available to help diagnose the error.

For all XES exits, connectors should establish the appropriate recovery to handle errors.