This document describes the difference between the Job Control Submenu commands Cancel/Abort and Cancel/Abort All. These commands are available when you choose Job Activity > Job Control.
There are no specific requirements for this document.
The information in this document is based on the Tidal Enterprise Scheduler versions 5.3.1 or later.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Both of the commands only affect the jobs in the selected production schedule. The Cancel/Abort All applies to jobs that have multiple instances (repeating jobs).
Cancel/Abort—Prevents or stops a job from running in the production schedule.
Cancel/Abort All—Prevents all instances of a job that are not complete from running in the production schedule.
When you choose Cancel/Abort All, you can choose whether to release the dependents of the chosen job. If you choose to release, the dependent job is no longer dependent on the jobs that you cancel or abort.