The LOGON command establishes a Teradata SQL session with Teradata Database.
The ACCEPT and SET commands are valid commands preceding LOGON and LOGTABLE commands.
Note: To prevent the password from appearing in the script, use Teradata Wallet. Refer to Security Administration (B035‑1100) and the appropriate installation guide for more information.
Standard LOGON Syntax
Note: On the z/OS platform, with the use of the User Logon Exit routine in TDP, the user name is not required. See the Teradata Director Program Reference (B035‑2416) for more information.
Single Sign‑on LOGON Syntax
Note: On the Windows platform, if logon encryption is enabled on the gateway, then single sign‑on is disabled on the client and standard logon syntax should be used instead
where:
Syntax Element |
Description |
acctid |
Account identifier associated with the username An account identifier can have up to 30 bytes. If an acctid is not specified, FastExport uses the default identifier defined when the user was created. |
password |
Password associated with the username A password can have up to 30 bytes. Note: Passwords that contain special characters must be enclosed in double quotes. The strings in double quotes will not be touched in the LOGON command. |
tdpid |
Optional character string that identifies the name of a TDP If the tdpid is not specified, FastExport uses the default TDP established by the system administrator. Note: For mainframe‑attached systems, the tdpid string must be in the form: TDPn where n is the TDP identifier. |
username |
User identifier of up to 30 bytes |
Note: The period preceding the LOGON command is optional.
Table 40 describes the things to consider when using the LOGON command.
Topic |
Usage Notes |
Command Frequency and Placement |
A LOGON command is required for each invocation of the FastExport utility. One LOGON command is allowed for each invocation of the FastExport utility, and it must precede any other FastExport commands except RUN FILE command and LOGTABLE command. |
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 LOGON, if the Gateway to Teradata Database is configured to use single sign‑on (SSO), and the Teradata client machine has already been logged on, the machine name, user name, and password are not required in the LOGON command. The user name and password combination specified when the Teradata client machine was logged on are authenticated via network security for a SSO 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. To connect to a Teradata Database other than the one currently logged on, the TDPid must be included in the LOGON command. If the TDPid is not specified, the default contained in clispb.dat will be used. For information about setting defaults, see the Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems (B035‑2418). To be interpreted correctly, the TDPid must be followed by the slash separator (‘/’), to distinguish the TDPid from a Teradata Database username. For example, to connect to slugger, enter one of the following: .LOGON slugger/; .LOGON slugger/,,'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 FILE commands used to identify the file containing the LOGON command. If the LOGON command is entered first, FastExport warns that the LOGTABLE command is also required. Note: When Teradata FastExport attempts to connect the Main SQL session the first time and the Teradata Database is down, Teradata FastExport displays an error message and terminates. Note: When Teradata FastExport attempts to connect the Auxiliary SQL session, or the data sessions and the Teradata Database is down. Teradata FastExport will retry to connect 16 times; if the Teradata Database is still down, Teradata FastExport displays an error message and terminates. |
The following example presents both the LOGON and LOGTABLE commands as they typically occur:
.logtable logtable001;
.logon tdpx/me,paswd;