15.10 - Calls to DBCHCL - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

prodname
Call-Level Interface Version 2
vrm_release
15.10
category
Programming Reference
featnum
B035-2417-035K

Before calling DBCHCL for the Connect function, applications can build a logon string and provide its address in Logon Pointer. A logon string has the following format:

[tdpid/]userid, password[, ‘acctid‘]        

where:

 

Syntax element...

Is the ...

tdpid

TDP id, which is the name of the TDP to be used to reach the Teradata Database.

Under z/OS, the tdpid is the subsystem name of the target TDP subsystem.

Unicode® Delimited identifier (U&"..."), with or without Unicode® escape sequences (/nnnn), or the Teradata "..."XN notation may not be used for the TDPid.

If only one character is specified, it is assumed to be an abbreviation for a four character TDP identifier that begins with TDP, and the omitted characters are supplied. Note that such abbreviation is deprecated, and its use is not recommended.

userid

The userid on the corresponding Teradata Database.

The maximum length of userid is 30 characters and is not case-specific.

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 UTF-16). Unicode® Delimited identifier (U&"..."), with or without Unicode® escape sequences (/nnnn), or the Teradata "..."XN notation may not be used for the TDPid. Therefore, the maximum length is 94 bytes.

Note that SQL terminal symbols (such as apostrophes) must always come from the shortest repertoire, that is, single-byte, 2 for UTF-16, unaccented Latin characters, except for UTF-16. Terminal symbols are never 3 bytes.

The dollar sign ($) is allowed anywhere in the userid.

The Logon Pointer field supports Teradata Wallet keywords. See “Teradata Wallet Support” on page 114.

password

The password on the corresponding Teradata Database.

At sites with an exit routine to add a password, the password may not be required.

The maximum length of a password is 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 UTF-16). Unicode® Delimited identifier (U&"..."), with or without Unicode® escape sequences (/nnnn), or the Teradata "..."XN notation may not be used for the TDPid. 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, single-byte unaccented Latin characters, except for UTF-16. Terminal symbols are never 3 bytes.

The Logon Pointer field supports Teradata Wallet keywords. See “Teradata Wallet Support” on page 114.

‘acctid‘

account id to be charged on the mainframe client.

The acctid may be omitted. If acctid is present, it may consist of as many as 30 characters, and it must be enclosed in apostrophes.

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

If the acctid includes an apostrophe, that apostrophe must be preceded by an apostrophe. Therefore, if the account string consists of 30 apostrophes, and is encoded in UTF-16 (2-byte terminal symbols), 124 bytes are necessary to specify the field. Unicode® Delimited identifier (U&"..."), with or without Unicode® escape sequences (\nnnn), or the Teradata "..."XN notation may not be used for the TDPid.

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

Any TDPid and delimiting slash consist of fixed-length characters from the session character set. If the character set supports multi-byte characters, they cannot be used for this information.