.png)
No Rescheduling
These properties control if and how this job uses time based rescheduling methods. When a job automatically starts as the result of having a start time set, the next start time is calculated based on the rescheduling algorithm specified with this job.
Every job that is rescheduled must have a calendar to examine. The calendar determines which days are skipped. Such things as do not run on holidays, what days are holidays, do not run on weekends, slide suppressed runs forward to the next available day or skip suppressed runs are all part of the calendar definition. To view or change these settings examine the calendar's property page.
No rescheduling: This means that this job will not reschedule on its own. It can still be initiated by other jobs and can also be submitted by a manual submit request.
|
This job is set to run at: |
This is the next time this job is set to run. If this field is set to "not set" then this job will not start unless initiated by another job or manually by a submit request from the user. All rescheduling rules only take affect when this job is activated, by setting this field to an initial date. |
|
The job has been run |
Each time the job is run this field, the up count, is incremented by one. You may set this to increase or decrease the up count. |
|
The job will be run |
Enter the number of times to run this job. Once it reaches ZERO automatic reruns are stopped. "Infinite" means allow any number of automatic reruns. "No runs left" is equivalent to zero. |