A job can be brought into the request queue once through schedule scan and executed more than once. Each iteration must successfully complete (or be forced complete) before the next iteration is added to the request queue. The following fields are used with repeating jobs:
Required. Specifies the amount of time between each iteration of the job.
Required. Specifies how the submit time requirement of each iteration is calculated-by adding the INTERVAL to the previous iteration's submit time requirement (CLOCK), START, or END time.
Optional. Specifies the maximum number of times the job will be repeated.
Optional. Specifies the clock time after which the job is not to be repeated. If not specified then the stop time will be 1439 minutes (24 hours minus one minute) after the submit time requirement of the first iteration.
Required. Specifies the due-out time (expected completion time) of the first iteration.
Required. Specifies the amount of time required to process the job.
Required. Specifies the submit time requirement of the first iteration.
As each iteration successfully completes (or is forced complete), CA WA CA 7 Edition adds the INTERVAL to the submit time requirement, start time, or end time based on the TYPE setting. This value becomes the next iteration's submit time requirement.
The new submit time requirement is then compared to the STOP time. If either the new submit time requirement or the current time are greater than the STOP time then the job is not repeated.
The new job's due-out time is calculated as the new submit time requirement plus the difference between the original due-out time and the original submit time requirement.
The new job's deadline time is calculated as the new due-out time minus the original lead time (LEADTM).
The start and end times of the job are local to the system where the job executed, not local to the system where CA WA CA 7 Edition is executing. TYPE=START and END should be used with care for NJE and cross-platform jobs.
Once a repeating job is in the request queue, you can skip iterations by adjusting the job's submit time using the QM.3 (XUPD) command. For example, suppose a job is set to repeat every hour on the hour, but today only you want to skip the 11 a.m. and 12 noon iterations. After the 10 a.m. iteration completes, you can use QM.3 command to edit the job's early start time to 1300 (1 p.m.). The job then waits until 1 p.m. before continuing to repeat.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|