When you run an archive or retirement job, the job uses a script template to create one script for each table the job extracts data from. The script template includes a scripting language that is supported by Teradata. The script template includes parameters that the job fills in with values at run time.
The script template, TPT_EXTRACT_SCRIPT_TEMPLATE, is packaged as an Enterprise Data Manager API. Optionally, you can copy the script template and customize the scripting language and the parameters. The name of the script template is configured in the Teradata source connection.
The job uses the script template to substitute values for the parameters and creates one script for each table. The job uses
<Job ID>_<Table Name>.bcp
as the naming file convention to create the script. The job saves the scripts in the
<Data Archive installation directory>/webapp/tmp
directory. The scripts are temporary files that Teradata Parallel Transporter uses to process data for individual tables.
The scripts include query requests. Teradata Parallel Transporter optimizes and rewrites the query requests and runs the scripts. Teradata Parallel Transporter creates one BCP file for each table. The BCP file includes the query results. After the Teradata Parallel Transporter creates the BCP files, the job deletes the scripts.