Scheduler Job Start Conditions

A scheduler job starts to run every time certain start conditions are fulfilled. You use start conditions to schedule jobs and trigger automatic job execution.

You set start conditions to the instances of a job definition, or jobs, when you create a scheduler task for that job definition. The start conditions you set in the scheduler task apply to every job instance created from the job definition.

You can schedule a job to run when a particular time comes (time-based scheduling), or when an event is raised (event-based scheduling).

The following time-based start conditions are possible:

• Start once or periodically at a particular time (recurrent execution)

  • Start once

    The job runs once at the specified time.

    This is a special case of recurrent execution, in which the job has a single iteration, as opposed to the several iterations in the recurrent periodical start condition.

  • Start periodically

    The job runs once at a particular date and time and then runs recurrently again a specified number of times at specified regular intervals. You can exclude execution times from the schedule of a recurrent job so that it does not run at those times.

    The recurrent periodical job can run infinitely.

• Start once or periodically on a day relative to the start of the month, week, day, and hour (cron execution).

  With cron start conditions, you define the minute, the hour, the day of week and/ or month, and the year when you want the job to run.

  • Start once

    The job runs once at the specified time.

  • Start periodically

    The job runs at the specified intervals. You can set the job to run one or more times within a period of time that occurs at regular intervals. You can exclude execution times from the schedule of a cron job so that it does not run at those times.

The table below provides examples of the various time-based start conditions which you can use to schedule jobs.