JobScheduler Calendars provide a sophisticated method of specifying the days 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 days 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 Business Day Calender to be defined once and then specified as required.
The Calendar feature is introduced with JobScheduler FEATURE AVAILABILITY STARTING FROM RELEASE 1.12 and will replace Schedules,
Calendars are configured as either working days or non-working days:
- A working day Calendar specifies the business days for which job executions are targeted.
- Non-working days include days for which jobs should not be executed.
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:
- Weekdays: Monday to Friday, every week,
- Recurring Day; every 2nd last day in every month,
- National Holidays: for a country for the a particular year.
Frequencies can be inclusive and exclusive, allowing a number of approaches to Calender configuration to be adopted in line with legacy procedures.
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.
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.
Calendars for Orders, Jobs and Schedules
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.