Setting Up the BTEQ Scripts and Run Program Executables - Teradata Viewpoint

Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Viewpoint
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
iwr1478709689896.ditamap
dita:ditavalPath
2207_ICUCustomer_vp_1610.ditaval.ditaval
dita:id
B035-2207
lifecycle
previous
Product Category
Analytical Ecosystem
The Teradata Notification Service for Linux executes the BTEQ and Run Program alert actions. The BTEQ scripts and program executables must be located in specified directories.

The directories where you placed the BTEQ scripts and programs are scanned periodically by the Teradata Notification Service while the service is running. If changes are detected to the directories, the updated directory contents are relayed to the alert service, which updates the Teradata Alerts repository on the Viewpoint server. The alert service must be running on the Viewpoint server in order for updates to be visible on the Viewpoint server.

The following directories are created during the installation and preserved during upgrades. The system administrator should ensure these directories have the appropriate permissions set for the service user (default is “camuser”) effective user ID for the tdnotification service.
/opt/teradata/client/cam/sql
/opt/teradata/client/cam/usrcmd
During the installation, the following symbolic links are created:
  • /opt/teradata/client/16.10/cam/tdnotification/sql -> /opt/teradata/client/cam/sql
  • /opt/teradata/client/16.10/cam/tdnotification/usrcmd -> /opt/teradata/client/cam/usrcmd
  1. Log in to the server as the root user.
  2. Place the BTEQ scripts in: /opt/teradata/client/cam/tdnotification/sql
  3. Ensure BTEQ scripts have at least 744 file permissions and are owned by the service user account.
  4. Place the programs you want to run in: /opt/teradata/client/cam/tdnotification/usrcmd
  5. Ensure the programs have at least 755 file permissions and are owned by the service user account.