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.
Object class: Schedule object
Object type/Short form: JSCH
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.
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:
-
Defining the Period Duration, which is the time frame that determines the regularity with which the tasks are executed
You define it on the Attributes Page. Tasks are executed once within a period.
-
Defining specific time parameters for the tasks included in the Schedule
For example, task start time and offset in relation to the period specified for the Schedule. If necessary, you can modify certain properties of the tasks. You define it on the Schedule page. For more information, see Defining Schedule Objects.
-
The Period Turnaround Time, which is the time at which completed tasks are removed from the Schedule. The same tasks are reloaded for the same period
You define it on the Attributes Page.
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:
- Notifications
- Events
- File transfers
- Groups
- Workflows
- Remote Task Manager
- Jobs
- Scripts
Schedule objects typically have one of the following statuses:
- Active, when the Schedule is enabled.
- Stopped, if you select the Suspend option for the Schedule.
The status of both the Schedule and of its tasks is visible in the Process Monitoring perspective.
This list provides a quick overview of the steps to carry out when working with schedule objects and of the available functions:
- Create a Schedule and add executable objects to it.
-
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.
- Optionally, specify individual start times, offsets, and calendars for specific tasks. This parameter allows or denies their execution.
-
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.
- 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.
- The schedule is still running
See also: