Using the Job Identifier in Your Job Script - Parallel Transporter

Teradata® Parallel Transporter User Guide - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Parallel Transporter
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-08-25
dita:mapPath
uzp1645128359760.ditamap
dita:ditavalPath
tvt1507315030722.ditaval
dita:id
B035-2445
Product Category
Teradata Tools and Utilities

Teradata PT constructs a unique identifier for each job submitted for execution. Even though it is not generated until your job executes, you can reference its unique job identifier in your job script via the new script keyword $JOBID and $$JOBID.

  • Use $JOBID to get the job identifier as a quoted string.
  • Use $$JOBID to get the job identifier as an unquoted token but with the underscore character replacing the hyphen between the job name and the job sequence number.

For example, $JOBID becomes 'ws150002-02335' and $$JOBID becomes ws150002_02335.

The $JOBID and $$JOBID feature allows you to use the unique Teradata PT-constructed job identifier in the names of script items, which can be especially useful for items that persist after job execution such as log files.