Designating Non-Target Systems - Teradata Data Mover

Teradata Data Mover User Guide

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

You can prevent one or more Teradata Database systems from being a target system for a Data Mover job. This configuration option enables you to avoid accidentally running a job in which data is copied to an unintended target system.

The systems may be specified either by their TDPID hostnames or their IP addresses, but must be consistent with your system specification in any Data Mover commands. For example, if you specify systems by using their IP addresses for Data Mover commands, you must specify non-target systems by their IP addresses.

  1. Run the list_configuration command to generate configuration.xml.
  2. Open configuration.xml for editing.
  3. For the key job.never.target.system under the <property> element, set the <value> element to true. The default value for this key is false.
  4. Add the <systemList> element under <value>.
  5. For each non-target system, add a <targetSystem> element and enter the hostname TDPID or IP address of the system.
  6. Close the entry with the </targetSystem> element.
  7. Save configuration.xml and run the save_configuration command to update the daemon with the new list of non-target systems.
In the following example configuration.xml, the Teradata Database systems with TDPID hostnames PROD2 and PROD3 cannot be used as target systems.
<property>
 <key>job.never.target.system</key>
 <value>true</value>
  <systemList>
   <targetSystem>PROD2</targetSystem>
   <targetSystem>PROD3</targetSystem>
  </systemList>
</property>