Schedules (JSCH)

Schedule objects are a powerful and flexible tool to design both time and event-driven task management. They allow you to define parameters that start tasks automatically at user-defined intervals. Schedules are the core automation objects.

This topic includes the following:

Tip: Have a look at Example: Scheduling Tasks with Time and Calendar Conditions: This example describes how to set up a Schedule object in which the tasks should meet time constrains.

Overview

Schedule objects are efficient frames to collect tasks that you want to execute at regular intervals. They define scheduling parameters, such as the periodicity with which the tasks are executed and the times at which they start. They also allow you to modify the properties of their tasks. Such changes apply to the tasks only when processed within the Schedule, the objects themselves are not affected by them.

Designing Schedule objects involves:

Usually, a Schedule object is associated to a Calendar that establishes pre-conditions for executing it. The Calendar defines a constraint to the period that is defined in the Schedule. For example, a task is executed with the regularity that is defined in the Period Duration but only on working days. For more information, see Calendars (CALE)

The period duration and the period turnaround time are cyclical tools that are specific to the Schedule as a whole. Start times and Calendars are defined specifically for each child task.

Objects Automated through Schedules

Schedule objects can handle the automatic processing of the following object types and their sub types:

Schedule Statuses

Schedule objects typically have one of the following statuses:

The status of both the Schedule and of its tasks is visible in the Process Monitoring perspective.

Working with Schedule Objects

This list provides a quick overview of the steps to carry out when working with schedule objects and of the available functions:

  1. Create a Schedule and add executable objects to it.
  2. Define a Duration Period and a Period Turnaround Time for the entire Schedule.

    For example, if the duration is one day and the turnaround time is midnight, each task is executed once a day and loaded again at midnight.

  3. Optionally, specify individual start times, offsets, and calendars for specific tasks. This parameter allows or denies their execution.
  4. Execute it manually for the first time to activate it, see Activating Schedule Objects.

    Immediately after executing it, the Monitoring option is available when you select and right-click the Schedule object. This option opens the list of Tasks in the Process Monitoring perspective. A filter is pre-set so that only this particular task is displayed in the list. This function helps you check whether the Schedule is performing as you expect.

  5. Open the Schedule Monitor (see Monitoring Schedules). Two scenarios are possible here:
    • The schedule is still running

      You can restart tasks, open their monitor (reports and execution data) and call their details. You can also modify some of its parameters. These modifications apply to only this execution. For more information, see Modifying Active Schedules and Modifying Tasks in an Active Schedule.

    • The schedule has already finished

      The properties of the tasks are in read-only mode and cannot be modified. You can restart tasks, open the Schedule monitor, access its reports and execution data, and so on.

See also: