When you configure Teradata Alerts to run a BTEQ script as an alert action, it creates a logon session with the Teradata system, runs the script to completion, and ends the session. Teradata Alerts processes BTEQ scripts sequentially as shown in the table below.
| BTEQ Command | Description | Details | Executed |
|---|---|---|---|
| .LOGON. | Creates a logon session | Enters the TDPID, Account ID, Username and Password that you used when creating the BTEQ configuration Because you define login credentials in the Alert Setup portlet, make sure that BTEQ scripts do not contain the .LOGON. command.
|
Automatically |
| .LOGMECH. | Provides extra information for a logon session | Enters the optional Logmech Name | Must define Logmech Name when creating the BTEQ configuration |
| .LOGDATA. | Provides extra information for a logon session | Enters the optional Logmech Name and the corresponding Logmech Data | Must define Logmech Name and the corresponding Logmech Data when creating the BTEQ configuration |
| .RUN FILE. | Executes the BTEQ script | Executes the commands in the BTEQ script in InstallFolder\Teradata\Client\16.20\Teradata Notification Service\sql that is available from the Script list when you created a BTEQ action set | Automatically |
| .QUIT. | Logs out of the session | Automatically |