Default Checkpoint File Names - 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
dita:id
B035-2445
lifecycle
previous
Product Category
Teradata Tools and Utilities

Each Teradata PT job automatically creates three associated checkpoint files during job execution and places them in the specified checkpoint directories. These files extend across multiple job steps, if the job has more than one step. They are automatically deleted after a job runs all the way to completion without errors, but if any step fails to finish successfully, the checkpoint files are not deleted and remain in the checkpoint directory.

Default name formulas for the standard job checkpoint files vary by operating system as follows:

On UNIX and Windows platforms:

  • <job identifier>CPD1
  • <job identifier>CPD2
  • <job identifier>LVCP

where <job identifier> is the job name from the tbuild command line, if a jobname was specified, or the userid in the job logon, if a job name was not specified.

On z/OS platforms, the checkpoint datasets have the following DDNAMEs:

  • //CPD1
  • //CPD2
  • //LVCP