The adapter SET CONNECTION_ATTRIBUTES command enables users to identify themselves to the Teradata RDBMS. When adapter users issue the command at the beginning of a FOCUS session, Teradata verifies their authorization to access tables and views.

Note: DBCLOGON is a synonym for CONNECTION_ATTRIBUTES supported for compatibility with earlier releases of the adapter.

The SET CONNECTION_ATTRIBUTES command must be issued before any DBC/SQL commands or FOCUS requests that require Teradata services. Internally, the adapter stores the Teradata logon ID and password in the virtual storage space for the user. The DBC authorization process is deferred until a subsequent command for Teradata services is executed. The adapter initiates the logon immediately prior to executing a request for Teradata services by the user.

The SET CONNECTION_ATTRIBUTES command may be issued from the FOCUS command level or be included in any FOCUS-supported profile. The syntax is

ENGINE [SQLDBC] SET CONNECTION_ATTRIBUTES connection_name/userid,passwd 
[;]

where:

SQLDBC

Is required if you did not previously issue the SET SQLENGINE command for Teradata (see Direct SQL Passthru).

connection_name

Is the Teradata Director Program ID (TDP ID). Valid values are site-specific and release-dependent.

Note: Specifying a TDP ID may not be necessary at your site. Contact your database administrator for the requirements at your site.

userid

Is your Teradata user ID, up to 30 characters long.

passwd

Is the associated Teradata password, up to 30 characters long.

Note: If there is no password for the connection, the userid must still be followed by a comma.

If the SET CONNECTION_ATTRIBUTES command is rejected, a DBC error message is generated, and the user should resubmit the command with correct information.

For additional security, a Dialogue Manager procedure can prompt the user for the Teradata password using -CRTFORM or -PROMPT commands, and store the password in a variable. The -CRTFORM command also provides a non-display option. For information about Dialogue Manager, see the Developing Applications manual.