Usage Notes - MultiLoad

Teradata® MultiLoad Reference

Product
MultiLoad
Release Number
16.20
Published
October 2018
Language
English (United States)
Last Update
2018-10-10
dita:mapPath
lsl1527114222348.ditamap
dita:ditavalPath
Audience_PDF_product_tpt_userguide_include.ditaval
dita:id
B035-2409
lifecycle
previous
Product Category
Teradata Tools and Utilities

The following table describes the things to consider when using the LOGON command.

LOGON Usage Notes 
Topic Usage Notes
Logon Parameters For standard logon, the parameters (tdpid, username, password, and acctid) are used in all sessions established with Teradata Database. The LOGON command may occur only once.

For single sign-on, if the Gateway to Teradata Database is configured to use single sign-on (SSO), and are already logged on to a Teradata client machine, then the machine name, user name, and password are not required in the LOGON command. The user name and password combination which were specified logging onto a Teradata client machine are authenticated with network security for a single sign-on such that valid Teradata users will be permitted to log on to Teradata Database. The use of SSO is strictly optional, unless the Gateway has been configured to accept only SSO-style logons.

On z/OS, with the use of User Logon Exit routine in TDP, userid is not required. Otherwise, userid is required. See Teradata Director Program Reference (B035-2416) for more information.

To connect to a Teradata Database system other than the one currently logged onto, the tdpid must be included in the LOGON command. If the tdpid is not specified, the default contained in clispb.dat will be used. Refer to Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems (B035-2418) for information about setting defaults.

To be interpreted correctly, the tdpid must be followed by the slash separator (‘/’), to distinguish the tdpid from a Teradata Database user name. For example, to connect to serverxyz, enter one of the following:

.LOGON serverxyz/;

.LOGON serverxyz/,,'acctinfo';

If an account ID is to be used, the optional account ID must be specified in the LOGON command.

Using LOGON with the LOGTABLE Command Both the LOGON and LOGTABLE commands are required.

LOGON and LOGTABLE commands may appear in any order, but must precede other commands except RUN commands used to identify the file containing the LOGON command.

If the LOGON command is entered first, Teradata MultiLoad warns that the LOGTABLE command also is required.

When Teradata MultiLoad attempts to connect the Main SQL session the first time and the Teradata Database is down, Teradata MultiLoad displays an error message and terminates.
When Teradata MultiLoad attempts to connect the Auxiliary SQL session, or the data sessions and the Teradata Database is down. Teradata MultiLoad tries to connect 16 times; if the Teradata Database is still down, Teradata MultiLoad displays an error message and terminates.