17.10 - Logon - Call-Level Interface Version 2

Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems

Product
Call-Level Interface Version 2
Release Number
17.10
Release Date
October 2021
Content Type
Programming Reference
Publication ID
B035-2418-061K
Language
English (United States)

Purpose

Establishes a session if the userid and password are valid

Usage Notes

If an account is not supplied, the default account for the user is used.

This parcel is generated by CLIv2 at the direction of the application.

Parcel Data

The following table lists field information for the Logon parcel.

Flavor Field Body Parcel Length Parcel Body Fields
36 278 LogonString: 5 to 128 bytes

Field Notes

LogonString is a character string containing the following elements:

userid, password[, ‘account’]

where the following is true:

The userid is the user’s identification. It must consist of at least one character and may consist of as many as 30 characters. Each character may require 1, 2, or 3 bytes, depending on the character set used. Therefore, up to 90 bytes may be necessary to specify the field. The userid may be enclosed in apostrophes, each of which requires 1 byte (2 bytes if Unicode®). Therefore, the maximum length is 92 bytes.

Note that SQL terminal symbols (such as apostrophes) must always come from the shortest repertoire; that is, 1 byte. Terminal symbols are never 3 bytes.

The userid and password must be separated by a comma.

The password is the user’s password. It must consist of at least one character, and may consist of as many as 30 characters. Each character may require 1, 2, or 3 bytes, depending on the character set used. Therefore, up to 90 bytes may be necessary to specify the field. The password may be enclosed in quotation marks, each of which requires 1 byte (2 bytes if Unicode). Therefore, the maximum length is 92 bytes.

Note that SQL terminal symbols (such as quotation marks) must always come from the shortest repertoire; that is 1 byte. Terminal symbols are never 3 bytes.

If the account is not omitted, the password and account must be separated by a comma.

The userid, password, and account name each consists of characters from the session character set.

When supported by the session character set, double-byte characters may be included by preceding each contiguous group of them with the Shift-out control character, X’0E’, and following this group with the Shift-in control character, X’0F’.

Any TDP identifier and delimiting slash must be specified in the standard ASCII character set.

Neither commas nor blanks may be specified as double-byte characters.

The password is usually required, but it may be optional in the logon string submitted by the application if the site has an exit routine that validates the userid.

The account (optional) is the account under which the user is logging on.

The account may consist of as many as 30 characters, and it must be enclosed in apostrophes. Any apostrophe in the account name must be represented by two apostrophes. The second apostrophe is not counted toward the limit of 30 characters.

Each character may consist of 1, 2, or 3 bytes, depending on the character set used.

If the account string consists of 30 apostrophes, and is encoded in Unicode (2-byte terminal symbols), 124 bytes are necessary to specify the field.

The userid and password must satisfy the lexical characteristics of Teradata SQL words.

See the description of lexical characteristics in Teradata Vantage™ - Database Design, B035-1094 and Teradata Vantage™ - SQL Fundamentals, B035-1141.