Specification of Security Attributes
The following security-related attributes may be required for logons to Teradata Database depending on the user authentication method employed.
Specifying Security Attribute Values
Values for the security attributes can be assigned in any the following statements, which are listed in the order they are processed, from lowest to highest priority.
Note: Specifying an attribute value at a higher priority level (an APPLY statement) supersedes values for the attribute specified at a lower level (a DEFINE OPERATOR statement).
Consider the following when deciding were to specify values for security attributes:
Teradata PT jobs log on to either the Teradata Database, an outside data source, or both. Logon requirements differ between Teradata Database and outside data sources.
When Accessing Non-Teradata Data Sources
The following operators access non-Teradata data sources. However, since they logon through an access module, they do not require logon information.
For these operators, logon information must be entered as part of the access module or INMOD/OUTMOD routine through which the operator accesses the outside data source.
Note: Although it also accesses outside data sources, the ODBC operator functions differently from other such operators, and allows the option of specifying the following in the job script:
For detailed information “ODBC Operator” in Teradata Parallel Transporter Reference.
When Accessing a Teradata Database
The following operators can directly access a Teradata Database and therefore require submission of more detailed logon information: