Non-target System Designation Scenarios | Teradata Data Mover - Scenarios for Non-Target System Designation - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.10
Published
June 2021
Language
English (United States)
Last Update
2021-06-16
dita:mapPath
fcu1619423186706.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
The following table describes what happens in specific scenarios with the job.never.target.system option.
Values Effect
The value of job.never.target.system is false, and no systems are defined under <systemList> Data Mover does not use this feature. This is the default setting.
The value of job.never.target.system is false, and non-target systems are defined under <systemList> Data Mover ignores the list of non-target systems.
The value of job.never.target.system is true, but no systems are defined under <systemList> Data Mover returns an error.
The value of job.never.target.system is true, a non-target system is defined under <systemList>, and you attempt to create a Data Mover job that copies data to that system Data Mover returns an error.
The non-target system defined under <systemList> is specified as an IP address, but the Data Mover command uses TDPID hostnames Data Mover ignores the IP address in the list of non-target systems because Data Mover commands are using TDPID hostnames. You must use the same type of system specification for Data Mover commands and for this list.