LOGON
Purpose
LOGON specifies the name of the Teradata machine that Teradata ARC should connect to, as well as the user name and password that should be used.
Note: A LOGON string that does not contain a userid and a password is interpreted as a SSO (single sign-on) logon.
Syntax
where
|
Syntax Element |
Description |
|
tdpid |
The identifier of the Teradata machine that will be used for this job Note: tdpid is followed by a “/”. The tdpid must be a valid identifier configured for the site. If a value is not entered, tdpid defaults to the id established by the system administrator. |
|
userid |
User identifier A userid can be up to 30 characters. Your userid must be authorized to perform the operations specified by subsequent utility statements. Note: This field is optional if single sign-on (SSO) is implemented |
|
password |
Password associated with the user name A password can be up to 30 characters. For a null password, include a comma before the semicolon. Note: This field is optional if single sign-on (SSO) is implemented |
|
’accid’ |
Account identifier associated with the userid If this value is omitted, Teradata ARC uses the default account identifier defined when your userid was created. |
Usage Notes
The LOGON statement causes Teradata ARC to log on only two control sessions for the user.
When Teradata ARC encounters ARCHIVE, RESTORE, or COPY, it automatically logs on any additional data sessions specified in the SESSIONS runtime parameter. ARCHIVE, RESTORE, and COPY are the only statements that need these sessions.
LOGON establishes sessions by:
When LOGON is accepted, this message is displayed:
2 SESSIONS LOGGED ON
If the user who is specified by userid is logged onto the Teradata Database through a program other than Teradata ARC, Teradata ARC terminates as soon as it encounters BUILD, COPY, RESTORE, ROLLBACK, or ROLLFORWARD. To determine whether a user is logged onto the Teradata Database, Teradata ARC performs a SELECT on database DBC.sessionInfo. Therefore, the user attempting to log on must have SELECT privileges on DBC.sessionInfo.
If a LOGON statement has already been run by Teradata ARC, Teradata ARC logs off all Teradata Database sessions from the previous logon.
The implementation of the SSO feature provides the ability to log onto a workstation once and then access the Teradata Database without having to provide a user name and password. SSO saves the time required to enter these fields, which are now optional. Additionally, certain authentication mechanisms (e.g., Kerberos, NTLM) do not send passwords across the network to further heighten security. SSO requires support of both the database and the client software.