16.20 - Defining the Job Header and Job Name - Parallel Transporter

Teradata® Parallel Transporter User Guide

Product
Parallel Transporter
Release Number
16.20
Published
August 2020
Language
English (United States)
Last Update
2020-08-27
dita:mapPath
uah1527114222342.ditamap
dita:ditavalPath
Audience_PDF_product_tpt_userguide_include.ditaval

A Teradata PT script starts with an optional header that contains general information about the job, and the required DEFINE JOB statement that names and describes the job, as shown in the following figure.

Job Header and Job Name

Consider the following when creating the job header and assigning the job name.
  • The Script Name shown in the job header is optional, and is there for quick reference. It can be the same as the jobname or it can be the filename for the script.
  • The jobname shown in the DEFINE JOB statement is required. It is best to use a descriptive name, in the case of the example script, something like “Two Source Bulk Update.”

    Note that the jobname shown in the DEFINE JOB statement is not necessarily the same as the “jobname” specified in the tbuild statement when launching the job, although it can be. The tbuild statement might specify something like “Two Source Bulk Updateddmmyy,” to differentiate a specific run of the job.

    For detailed information on tbuild and how to specify the job and job script, see Setting tbuild Options.