The Calendar feature is introduced with JobScheduler and will replace Schedules,
Calendars are configured as either working days or non-working days:
Both calendar types can be combined with precedence being given to non-working days for any overlapping days.
Handling of days in both types of Calendars is simplified through the use of Frequencies. Typical Frequencies include:
Frequencies can be inclusive and exclusive, allowing a number of approaches to Calender configuration to be adopted in line with legacy procedures.
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.
Once they have been configured, one or more Calendars can be assigned to Orders and Jobs as required.
Assigned Calendars can also be modified with modifications being applied to all objects that use the respective Calendar.
Note that similar to other Resources, e.g. Locks and Process Classes, Calendars are stored as objects in the file system. Calendars are managed with the JOC Cockpit, they are not editable using the JobScheduler Object Editor, JOE. Calendars are added to the inventory in the JobScheduler reporting database.
The calendar user interface can be used to define the Run-Times, i.e the days and times at which Orders, Jobs and Schedules are to be run. Here the Run-Time is saved as part of the configuration of the Order, 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.
Export and import functions allow the bulk deployment of Calendars, for example, when updating non-working day information on a production system.
The Calendar deployment procedure is described in the Calendar Management - Calendar Deployment article.