The Logon Pointer field specifies the address of the logon string for the session.
|Used by||Action Taken|
Before calling DBCHCL for the Connect function, the application program must build a logon string and provide its address in Logon Pointer. A logon string has the following format:
where the following is true:
|tdpid||one of the dbcnames in the workstation-attached client’s host file on the network. Both ip address and ip port format in tdpid are supported. Examples are listed as follows:
Simple machine names that are used as TDPids should be unique across multiple domains (that is, the high-level qualifier in the fully-qualified domain name should be unique).
For example, bteqdev.sandiegoca.teradata.com and bteqdev.northpole.hellokitty.com should not be used in the same job.
When a simple machine name is supplied and there is no corresponding entry in the local hosts file, gethostbyname() appends the default domain name as found in /etc/resolv.conf (for UNIX) or in Advanced TCP/IP Settings (for Windows). This is done to obtain a valid IP address from DNS.
If tdpid is omitted, CLI uses the default for dbcname in the SPB (see System Parameter Block (SPB) Processing).
|userid||the user’s id on the corresponding database computer. Maximum length of userid is 30 bytes (alpha characters are not case specific; dollar sign ($), pound sign (#), and underscore (_) are allowed anywhere in userid; numbers are allowed but the first character may not be numeric).
Logon strings can contain the Teradata Wallet keywords. See the Teradata Wallet Support section below.
|password||the password on the corresponding database computer. Maximum length of password is 30 bytes (alpha characters are not case specific; dollar sign ($), pound sign (#) and underscore (_) are allowed anywhere in userid; numbers are allowed but the first character may not be numeric).
The Logon Pointer field contains the address at the beginning of the logon string. The logon strings can contain the Teradata Wallet keywords. See the Teradata Wallet Support section below.
|acctid||the account to be charged on workstation-attached clients. Maximum length of acctid is 30 bytes.|
Logon Pointer always points to the beginning of the logon string.
Teradata Wallet Support
Teradata Wallet supports the secure storage of passwords, ids, and other logon string information on the client's computer. For an introduction to Teradata Wallet, refer to https://downloads.teradata.com/tools/articles/introducing-teradata-wallet
For detailed information on using Teradata Wallet, see the most recent version of Teradata Vantage™ - Advanced SQL Engine Security Administration, B035-1100.
For detailed information on Teradata Wallet installation and setup options, see the Teradata Tools and Utilities Installation Guide for the appropriate operating system.
Kanji characters used in userid, password and acctid are limited to a maximum of 30 bytes. Because Kanji characters may be double or triple bytes, the maximum length when counted in Kanji characters should be less than 30. For example, if the userid contains only double byte Kanji characters, the maximum length for userid should be 15 Kanji characters.
Kanji characters are only allowed in userid, password and acctid. Blanks, commas and slashes must be single byte characters.
Multibyte Character Support
When the session character set is KANJIEBCDIC5026_0I, KANJIEBCDIC5035_0I, or KATAKANAEBCDIC, double-byte characters may be included by preceding each contiguous group of them with the Shift-out control byte, X’0E’, and following this group with the Shift-in control byte, X’0F’.
When the session character set is UTF8, each character requires between one and three bytes.
When the session character set is KANJIEUC_0U, each character requires one or two bytes, each possibly preceded by a Single-shift-2, X'8E', or Single-shift-3, X'8F', control byte. So each character requires a total of between one and three bytes.
When the session character set is KANJISJIS_0S, each character requires one or two bytes.