Introduction
JobScheduler Calendars provide a sophisticated method of specifying the days and times of the day on which scheduling events are to occur. Calendars allow similar levels of complexity to that provided by other enterprise level workload automation applications thereby easing migration to JobScheduler.
Calendars are lists of days on which Orders, Jobs and Schedules are planned to be executed. Calendars can be defined as either working or non-working days and can be both combined and reused. An example of Calendar combination would be one Calendar specifying that a normal working week contained the five days Monday to Friday being used in combination with a Calendar specifying the public holidays in the current year. Reuse allows, for example, a Holiday Calender to be defined once and then specified as required.
Scope
The Calendar feature is introduced with JobScheduler version 1.12
| Display feature availability |
|---|
|
and will replace
Schedules, which are deprecated in version 1.12 and will be removed with 1.13.
| Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | What will be deprecated? |
|---|
|
Description
General Description
Holiday Calendars
A day that is defined as a working day will be treated as a non-working day if it is listed in a holiday calender.
The treatment of a day that is defined as a non-working day will not be modified if that day is listed in a holiday calender.
Calendars as Resources
As resources, Calendars are managed in the Calenders tab of the Resources view of the JOC Cockpit. Resources are objects that can be configured independently of other objects.
...
Note that in contrast to the other Resources - Locks, Process Classes and Schedules - Calendars are not stored as XML objects on the file system. This means that they are not editable using the JobScheduler Object Editor, JOE. Calendars are permanently saved in the JobScheduler reporting database tables.
Calendars for Orders, Jobs and Schedules
The calendar interface can be used to define the Run Times - i.e the days and times at which Orders, Standalone Jobs or Schedules are to be run. Here the Run Time is saved as part of the configuration of the Order, Standalone Job or Schedule in XML format in the JobScheduler's live folder. Run Times set in this manner are persistent - that is, they will not be lost after a restart of the JobScheduler. They can also be read and edited using JOE, the JobScheduler Object Editor.
...