Overview of Reactivity
Robot Schedule lets you schedule jobs that run only after certain prerequisite conditions occur. These jobs are called reactive jobs because they react to conditions. Note: Reactive jobs are set up in the Explorer or IBM i versions of Robot Schedule.
A prerequisite job can be a Robot Schedule job, a batch job, a job on another system, or a job on a remote Skybot Scheduler server. Before the reactive job can start, the prerequisite job must return the specified status code. The status can be normal completion, abnormal termination, either normal completion or abnormal termination (this includes jobs that return a "W" completion status), submitted, running, delayed by OPAL, skipped by OPAL, or pending OPAL.
A reactive job can run only when its prerequisites are satisfied. However, a reactive job can also be limited by a run schedule. There are three options:
-
Prerequisites are specified, but not a run schedule: The job runs every time its prerequisites are met.
When all prerequisites are met, the job runs and the completion statuses on the prerequisite list are cleared.
-
Prerequisites are specified, and so are run days or dates: The job runs only if it's scheduled for that day.
When all prerequisites are met, Robot Schedule checks whether the job is scheduled to run that day. If it is, the job runs. Robot Schedule clears the completion statuses on the prerequisite list whether the job runs or not. Thus, the last of its prerequisites must happen on a run day or the reactive job does not run.
-
Prerequisites are specified, and so is a schedule with run days and times: The job runs at its next run day and time if its prerequisites are met.
Each day and time that the job is scheduled to run, Robot Schedule checks whether all prerequisites for the job are satisfied. If they are, the job runs. If they're not, Robot Schedule sends a warning message that the job was scheduled to run, but prerequisites were not met.