What happens to jobs that are not completed when the next new‑day autoscan occurs? The answer to this question depends on whether the job is eligible for backlogging.
Jobs that are unable to start on the day they are selected and have Backlog=YES in their profile (or default to Backlog=YES through their Jobset profile) are backlogged. When an unfinished job is backlogged, it remains in the tracking file as part of the workload for the following day and is automatically rescheduled for processing.
Jobs that are unable to run on the day they are selected and which have Backlog=NO in their profile (or default to Backlog=NO through their jobset profile) are automatically canceled and purged from the tracking file as part of the new‑day autoscan.
Jobs that are running when the new day’s autoscan occurs and have Backlog=RUNNING in their profile are backlogged. When a running job is backlogged, it remains in the tracking file as part of the workload for the following day and is automatically rescheduled for processing. If the job is not running during the autoscan, the job is removed from the tracking file.
Note: The time of the new‑day autoscan should occur after the expected completion of all scheduled jobs. This makes the Backlog option more meaningful. If the new‑day autoscan runs before the day’s work is completed, all unfinished jobs are purged or backlogged.
|
Copyright © 2010 CA.
All rights reserved.
|
|