Order of invocation
Each of the exits in the file control recovery program might be invoked during an attempt to backout a file update. If the backout fails, each exit might be re-invoked when the backout is retried. If an exit program needs to determine whether it is being invoked during the original backout attempt, or during a retry, it can check the value of the RE_ATTACHED_TRANSACTION field returned by an XPI INQUIRE_TRANSACTION call.
The way in which the exits interact, and the order in which they
are invoked, is shown in the following list. Assuming that all the
exits are enabled, for each backout attempt or retried backout attempt:
- If an open during backout fails, XFCBFAIL is invoked. None of the other exits is invoked.
- If the SHCDS PERMITNONRLSUPDATE command has been issued for the data set being backed out, XFCBOVER is invoked. If it returns UERCNORM (do not perform the backout), no further exits are invoked.
- Unless item 1 applies, or XFCBOVER has been invoked and returned UERCNORM, XFCBOUT is invoked.
- Backout issues a read update request for the record being backed
out.
If the read update fails, XFCBFAIL is invoked, followed by no further exits.
- If the update to be backed out was a write to a data set which does not support physical deletes (that is, a BDAM data set or a VSAM ESDS), XFCLDEL is invoked.
- If a failure occurs after this point, XFCBFAIL is invoked.