Purpose
The abort_job command aborts an actively running job, a job in the queue, or a job that is not responding.
Syntax
abort_job -n|-name Name [parameters]
Examples
dsc abort_job -n job1 -S
dsc abort_job -B -S
Parameters
- n|name Name
- The name of the job on which to perform the action. Must be unique for each job.
- O|override
- [Optional] Can only be used for backup, restore, and analyze_validate jobs. A Teradata job must be in the aborting phase. Overriding the abort_job only changes the status in the repository and does not affect the database.You should only use the override parameter when a job hangs, so that DSC resources can be freed to run other jobs.
- S|Skip_prompt SkipPrompt
- [Optional] Skips displaying a confirmation message before performing the command action.
- B|repository_backup Repository Backup
- [Optional] Aborts any running DSC repository job. The name of the job is not required when this parameter is used.
- u|user_authentication user
- Required when security management is enabled. Supplies the command with the Viewpoint user, and triggers a password prompt for authentication.
Usage Notes
There are two phases to aborting a job: aborting and aborted. The aborting phase releases media devices to the pool. The aborted phase releases node stream limits.
If the abort_job command is given for a job in queue to run, the job is removed from the queue. If the job is running when the request is sent to abort the job, it can take several minutes for the job to completely stop.
XML File Example
This command does not support an XML file.