Because recovery monitoring can be resource intensive, ARF was designed so that the recovery needs of a production job are tested at a limited number of points during CA WA CA 7 Edition processing. These tests are executed only if they are specifically indicated in the definitions of ARF conditions that are associated with the job when it enters the request queue. These points include: job submission, SMF feedback, late prompting, and job completion.
The definitions that provide the criteria for ARF tests are bundled into groups known as ARFSETs. All of the tests that ARF will use to monitor the status of a job are determined by the ARFSET that is associated with the job when the job enters the request queue.
An ARFSET can be associated with a job in several ways. An ARFSET can be named on the job definition panel. This can be overridden using the #ARFSET statement in the JCL or PARM data. Both of these designations can be overridden using the ARFSET keyword on the DEMAND command.
For internal cross-platform jobs, each job has only one step. With this step data, the completion information contains only the node name where the job executed, instead of the program name, proc name, or step name. Because jobs can be routed to an alternate node, if defined, these fields may not be reliable in any ARF conditional testing. Consider this impact if defining ARFSETs for internal cross-platform job types.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|