Purpose
The delete_job command deletes the specified job from the daemon. If an instance of a job is specified, that job instance is deleted. Before the job instance is deleted, a cleanup is performed, if required. If a job definition is specified, all job instances are deleted, but not the job definition itself. Before all job instances are deleted, a cleanup is performed on the last job instance, if required. There is also a parameter, all, to delete the job definition and all job instances.
Syntax
Parameters
See Parameter Order.
- all
- [Optional] Deletes job definition and all job instances.
- dm.rest.endpoint
- [Optional] Enter a Data Mover REST server URL to overwrite the default value specified in the commandline.properties file in order to connect to a different REST server (and therefore a different daemon) at runtime.
- job_name
- Name of the job to be deleted.
- security_password
- [Optional] Password for the super user or authorized Viewpoint user.
- security_password_encrypted
- [Optional] Encrypted password for the super user.
- security_username
- [Optional] User ID of the super user or authorized Viewpoint user. The user ID of the super user is dmcl_admin and cannot be changed.
- skip_prompt
- [Optional] Skips the prompt that confirms deletion.
XML File Example
For the delete_job command, type datamove delete_job -f parameters.xml.
In the following example, the parameters file deletes the job definition and all job instances for dmdev_to_floyd-Tue_Aug_25_06:15:56_EDT_2009 and skips the prompt that confirms deletion.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dmDeleteJob
xmlns="http://schemas.teradata.com/dataMover/v2009"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.teradata.com/unity/datamover.xsd">
<job_name>dmdev_to_floyd-Tue_Aug_25_06:15:56_EDT_2009</job_name>
<all>true</all>
<skip_prompt>true</skip_prompt>
</dmDeleteJob>