Table of Contents

Search

  1. Preface
  2. Introduction
  3. Working with Enterprise Data Manager
  4. Enterprise Data Manager
  5. ILM Repository Constraints
  6. Partition Exchange Purging
  7. APIs
  8. Salesforce Accelerator
  9. SAP Application Retirement Entities
  10. Import Formats for Constraints
  11. Glossary

Enterprise Data Manager Guide

Enterprise Data Manager Guide

Script Template Parameters

Script Template Parameters

The Teradata Parallel Transporter script template includes default parameters. The archive or retirement job replaces the parameters at runtime when the job creates scripts for tables.
The default parameters are required. No additional configuration is needed. Optionally, you can add parameters to the script. For example, you may want to use a different login name. You can use any property from the Teradata source connection as a script parameter. To add a parameter, use the technical name from the AM_DATA_REP_ATTR table in the ILM repository.
The script template includes the following required parameters:
&TABLE_NAME
Table name that the job needs to export data from.
&JOB_ID
Job ID of the archive or retirement job. Teradata Parallel Transporter uses the job ID as part of the BCP file name.
&DIR_PATH
BCP file staging directory in the Teradata source connection.
&TDPID
Host name in the Teradata source connection.
&SESSION
Maximum number of parallel sessions in the Teradata source connection.
&USER_NAME
Application login name in the Teradata source connection.
&PASSWORD
Password for the application login name in the Teradata source connection.
&SELECT_STMT
SQL select statement that the job creates to extract the data from Teradata.
&FILE_NAME
Name of the BCP file that the Teradata Parallel Transporter creates. By default, the job uses the following convention to create BCP files:
<Job ID>_<Table Name>.bcp

0 COMMENTS

We’d like to hear from you!