adTempus provides the capability of restarting jobs that were interrupted due to a system shutdown or failure. In such cases, though, you may not want to start executing your task from the beginning in the event of a restart.
For example, if you have a batch file that executes several different steps, you may want to skip the steps that completed before the failure.
Checkpoints provide a means of doing this. As your program, batch file, or script executes, it can periodically pass a checkpoint value to adTempus (this can be any string that will be meaningful to your program). If adTempus subsequently restarts the job after a failure, it will pass back the latest checkpoint it received; your task can use that to resume execution at the correct place.
The method for getting and setting the checkpoint depends on the kind of task you are executing:
Batch files should use the adtChkpt utility program.
Scripts (as long as they are run by an adTempus Script Execution task) can use the global Checkpoint variable.
Applications can retrieve the checkpoint by using Windows API functions to retrieve the "ADJobCheckpoint" environment variable. To set the checkpoint the application must use the automation interface to the adTempus engine.