The Teradata PT has a facility to start a job at the job step specified with tbuild command option -s:
tbuild -f <filename> -s <job step identifer>
where <job step identifier> is the job step name in the job script, or the implicit step number, 1,2, ..., corresponding to the top-to-bottom order in which the steps are defined in the script.
There are two ways to restart from a job step:
- If you specify a job step before the step that was interrupted, or the interrupted step itself, the job will restart at the interrupted step, using either of the following: the default Start-of-Data checkpoint (if no checkpoint interval was originally specified) or the last interval-driven checkpoint taken during the step. In these cases, the result is the same as if the tbuild command option -s had not been specified
- If interval checkpointing was not specified in the tbuild statement that launched the job, the job will restart from the default Start-of-Data checkpoint for the step.
- If interval checkpointing was specified in the tbuild command that launched the job, the job will restart from the last interval checkpoint before the failure.
- If you specify a job step beyond the step that was interrupted, then the job will restart at the specified step; any unfinished work in the interrupted step will not be completed, and any other job steps between the interrupted step and the specified step will not be executed. This approach would likely produce bad results and is not recommended.
Teradata recommends that you do not use the tbuild-s option to restart a job from a job step unless you are fully aware of the how it will affect the job.