save_job_scripts - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
kmo1482331935137.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

Purpose

The save_job_scripts command saves all the scripts in the scripts file to the daemon, which does not verify the scripts. Therefore, ensure the scripts' accuracy before saving.

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.
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.
dm-server1
dir
Input directory for the job scripts file referenced by the command description XML.
/home/datamover/scripts
filename.xml
Name of the job scripts XML file.
job2_script.xml
The name of the job scripts file by default is <job_name>_script.xml.
job_name
Name of the job to be saved.
12315DFHJKS
security_password
[Optional] Password for the super user or authorized Viewpoint user.
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.
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

Scripts have timestamps that are used to detect whether a newer version of the script has already been saved. This avoids conflicts with simultaneous editing. If a newer version of the script is detected, a command prompt gives the choice to overwrite the script or update to the latest version.

XML File Example

For the save_job_scripts command, type datamove save_job_scripts -f <job_name>_script.xml. For example, to save all job scripts for the job 12315DFHJKS that are specified in 12315DFHJKS_script.xml, type datamove save_job_scripts -f 12315DFHJKS_script.xml.

In the following example, 12315DFHJKS_script.xml writes the scripts for job 12315DFHJKS to /home/datamover/scripts.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<dmSaveJobScript>
	<job_name>12315DFHJKS</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>