Recovery actions are scheduled when the exception is detected so that the action can be performed at or near the point of failure. Each occurrence of an exception condition can have up to seven distinct actions associated with it in the definition of the condition. The order in which the actions occur in the definition of the condition determines the order in which actions are executed.
Each exception is handled in the order that it is detected. Because recovery actions are executed serially for a given job, all of the actions for an exception occurrence must be completed before the actions of a later exception occurrence can be executed. Suppose, for example, that one step completion condition is detected and has two CA WA CA 7 Edition commands associated with it. ARF will begin processing the commands as soon as the exception is recognized. Also suppose that another step completion exception is detected for the same job while ARF is issuing commands for the first exception. In this case, responses associated with the second exception will not be executed until those associated with the first exception have been handled.
Responses for an ARF exception are executed on an internal terminal dedicated for use by ARF. Each response is translated into a CA WA CA 7 Edition terminal command or set of such commands. Since all CA WA CA 7 Edition terminal command input is logged to the CA WA CA 7 Edition Browse Data Set, all ARF recovery activity is thereby recorded.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|