If TDP uses any network communication to access the Teradata Database, the MVS Communications Server requires that you establish a full-function z/OS Unix environment. Refer to IBM z/OS Communications Server: IP Configuration Guide for details.
All NPs for one TDP must be associated with the same Logical-host id, which is defined using the Teradata Database Configuration Utility (B035-1102), specifying a Host Type Designator of 'IBM'. NPs are associated with a Logical-host using the Teradata Database Parallel Upgrade Tool, described by the Parallel Upgrade Tool (PUT) document appropriate to the Database operating system. PUT refers to NPs as "MF Network connections." When multiple Teradata Databases have Logical-host ids with NPs accessed by TDPs in the same MVS image, all these Logical-host ids must be unique.
Normal TDP operation expects that resolution of a Teradata standard format NP network name to an IP address has been defined to either the MVS local host, network Domain Name System or both. The standard Teradata form of an NP network name is database||NTCI||n||.domain, where database is the name assigned to a Teradata Database, || indicates catenation, n is a decimal integer ascending from 1 without any leading zeroes, unique for each NP configured in that database, and domain consists of any qualifiers needed to uniquely resolve the NP network name. For efficiency, names associated with the same Database should have contiguous values for n, but to accommodate failures or maintenance, gaps of up to 10 can occur. Larger gaps will prevent use of subsequent NPs.
Local Resolution for NP Names
HOST : ipaddr : database||NTCI||n :: ::where ipaddr is the numeric IP address, in IPv4 dotted-decimal notation, of a node on the Teradata Database that has been configured to support an NP, and database, ||, and n are as previously defined as the standard Teradata form of an NP network name. After changing ETC.HOSTS.LOCAL, run the MVS MAKESITE application. Refer to z/OS Communications Server: IP System Administrator's Commands for details.
ipaddr database||NTCI||n||[.domain]where ipaddr is the numeric IP address, in either IPv4 dotted-decimal or IPv6 colon-hexadecimal notation, of a node on the Teradata Database that has been configured to support an NP, and database, ||, and n are as previously defined as the standard Teradata form of an NP network name.
NP Port Name Resolution
NTCIMAST portnumber/udp
NTCIMAST portnumber/tcp
where portnumber is the decimal port number configured on the Teradata Database, which is normally 64432.IPv6 Addresses
If IPv6 addresses are to be used, then the z/OS IP stack must be configured to support dual operation (both IPv4 and IPv6). This is done in an MVS SYS1.PARMLIB(BPXPRMnn) member addressed by the current SYS1.PARMLIB(IEASYSnn) member containing a NETWORK statement specifying the DOMAINNAME(AF_INET6) operand.
About IPSEC
The Teradata Database requires that any security and privacy required for network communication is provided using IPSEC on both z/OS and the Teradata Database. Specifically, in the z/OS IP stack being used by TDP, both TCP traffic to and from the network port used by the Teradata Database, whose default is 64432, and UDP traffic to and from the dynamically defined network port used by the Teradata Database use IPSEC. The IPSEC specifics defined on z/OS must mirror the specifics defined on the Teradata Database. For details on z/OS IPSEC refer to IBM z/OS Communications Server: IP Configuration Guide and z/OS Communications Server: IP System Administrator's Commands.