This page describes some of the job-related features of adTempus.
adTempus can run programs, scripts, batch files, documents, etc.
adTempus also has native support for additional tasks:
adTempus can look at the exit code from a program to determine whether the program succeeded; you tell adTempus what kind of exit code indicates a successful run. For example:
Scripts to Determine Success
Some programs do not return a meaningful exit code. For such programs, you can use a simple script to tell adTempus whether the program succeeded. For example, a reporting program is successful if the report file exists after the program runs. Your job can include a small script that checks for the report file after the program runs, and based on that tells adTempus whether the job succeeded.
adTempus features multi-step jobs, which means that each job can execute any number of different tasks. For example, instead of having a job that runs a batch file that in turn runs several programs, you can have a multi-step job, with each step running one of the programs.
This approach has several advantages, including:
adTempus can be configured to automatically restart a job that was interrupted due to a system shutdown, and to run jobs whose execution was missed because the system was not running when the jobs were scheduled to execute.
Programs, scripts, and batch files that do complex or multi-step processing can pass application-defined checkpoints to adTempus to indicate their progress. If adTempus needs to restart a job (e.g., after a system failure) it can pass the checkpoint back to the application so that it can resume where it left off.