15.10 - Adding and Editing AP Entries in the hosts File - Teradata Tools and Utilities

Teradata Tools and Utilities for Apple OS X Installation Guide

prodname
Teradata Tools and Utilities
vrm_release
15.10
created_date
August 2016
category
Installation
featnum
B035-3129-125K
  1. Once the Application Processor (APs) are identified, use a text editor to open the client hosts file and add or edit the AP entries. Use the following syntax when adding entries to the hosts file:
    a.b.c.d dbcnameCOPn [aliasCOPn]
    a.b.c.d
    The Internet address is a four-byte numeric value that identifies an AP and its location on the network. An Internet address is assigned to each AP when the Teradata Database is configured.
    dbcname
    The Teradata Database using the AP is 1 to 70 characters in length. The first character must be alphabetic; where the remaining characters can be alphanumeric. The System Parameter Block file, %Program Files%\Teradata\Client\version\clispb.dat, lists dbc as the default dbcname. dbc can be assigned as the dbcname of a Teradata Database with which the client computer communicates. This simplifies network debugging and avoids problems when name servers become available. If the client computer communicates with more than one Teradata Database on the same TCP/IP LAN, use dbc as the dbcname for the more heavily used Teradata Database. Any other names can be used for any remaining instances of Teradata Database.
    COPn
    The parameter that assigns a number to a particular AP that the Teradata Database uses. COP is a fixed string of characters that must always be specified. The value of n can range from 1 to the total number of "APs" in a COP group. A COP group is a set of "APs" that operate together for a particular Teradata Database. "APs" in the same COP group share session balancing and session recovery. Each AP within a COP group must be assigned a unique number starting with 1.
    aliasCOPn
    The alias name, specifies an alternate name for a Teradata Database AP. Its use is optional. More than one aliasname is permitted. An aliasname need not be unique across a network, but the hosts file for a computer must not contain the same aliasname for more than one AP. Suggestion: the n in each alias COPn equals n in the corresponding dbcname COPn.
    For example, a client computer accesses one Teradata Database (named dbc) through two TCP/IP APs with addresses 101.0.0.21 and 101.0.0.22 on the same logical TCP/IP LAN. Each AP is assigned two alias names. The following lines show example entries in the hosts file for the two APs:
    101.0.0.21 dbcnode1 dbccop1 tdcop1
    101.0.0.22 dbcnode2 dbccop2 tdcop2