list_job_scripts | Commands | Teradata Data Mover - list_job_scripts - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.20
Published
November 2021
Language
English (United States)
Last Update
2021-11-04
dita:mapPath
wph1512683331242.ditamap
dita:ditavalPath
4101_UG_dm_1620.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

Purpose

The list_job_scripts command lists all Teradata ARC scripts that were created for the job. To modify job behavior, edit the scripts, then use the save_job_scripts command to save changes to the daemon. Ensure the accuracy of the edited scripts before saving them. The daemon does not verify changes.

If you specify the original job name for the list_job_scripts command, the scripts for the original job definition are listed. If you specify the name of a job instance in which job variables were modified at runtime, the scripts associated with the modified job definition are listed.

Parameters

See Parameter Order.

broker.port
[Optional] You may enter a broker port to overwrite the default value specified in the commandline.properties file in order to connect to a different ActiveMQ server (and therefore a different daemon) at runtime.
Example: 61616
broker.url
[Optional] You may enter a broker URL to overwrite the default value specified in the commandline.properties file in order to connect to a different ActiveMQ server (and therefore a different daemon) at runtime.
Example: dm-server1
dir
[Optional] Output directory for the scripts file. The directory will be created if one does not exist.
Example: /home/datamover/scripts
The generated XML file is written by default to the current directory.
filename
[Optional] Output file name for the scripts file. Existing file name will be overwritten.
Example: script.xml
The generated XML file has by default the name <job_name>_script.xml.
job_name
Name of the job to be edited.
Example: 12315DFHJKS
security_password
[Optional] Password for the super user or authorized Viewpoint user.
Example: 53cUr17y
Required if security management is enabled on the Data Mover daemon. Not a valid parameter if -security_password_encrypted is also specified.
security_password_encrypted
[Optional] Encrypted password for the super user.
Example: 052c7aabd14c7770141ac3c0137ab98ae0d3f0f7cddf588981206b010c0c1b2f
Required if security management is enabled on the Data Mover daemon. Not a valid parameter if -security_password is also specified.
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.
Required if security management is enabled on the Data Mover daemon.

Usage Notes

Following is an example of the output when the list_job_scripts command is used:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<dmSaveJobScript>
	<job_name>job1</job_name>
	<dir>/home/datamover/scripts</dir>
	<plan>
		<step>
		  <task id="3">
			   <timestamp>Fri Jul 10 21:52:55 PDT 2009</timestamp>
		    <archive_script>archiveScript_3</archive_script>
		    <copy_script>copyScript_3</copy_script>
 		 </task>
 		</step>
		</plan>
</dmSaveJobScript>

XML File Example

For the list_job_scripts command, type datamove list_job_scripts -f parameters.xml.

In the following example, the parameters file writes the steps for job1 to /home/datamover/scripts/job1_script.xml.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<dmListJobScript>
	<job_name>job1</job_name>
	<dir>/home/datamover/scripts</dir>
	<filename>job1_script.xml</filename>
</dmListJobScript>