Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 4

changes.mady.by.user Alan Amos

Saved on

compared with

New Version Current

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

Excerpt Include
Calendars
Calendars
nopaneltrue
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 JobScheduler 

Display feature availability
StartingFromRelease1.12
and will replace Schedules,

  • Jira
    serverSOS JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6dc67751-9d67-34cd-985b-194a8cdc9602
    keyJOC-267
  • Jira
    serverSOS JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6dc67751-9d67-34cd-985b-194a8cdc9602
    keyJS-1754

Description

General Description

Calendar Types

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.

Frequencies

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.

...

Description

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 in contrast similar to the other Resources - Locks, , e.g. Locks and Process Classes and Schedules - , Calendars are not stored as XML objects on in the file system. This means that Calendars are managed with the JOC Cockpit, they are not editable using the JobScheduler Object Editor, JOE. Calendars are permanently saved added to the inventory in the JobScheduler reporting database tables.

Calendars for Orders, Jobs and Schedules

Calendars The calendar user interface can be used to define the days on which an Order or a Schedule is Run-Times, i.e the days and times at which Orders, Jobs and Schedules are to be run. The RunTime - that is, the times within a day at which the Order or Schedule is to run - can either be set as for the Order or Schedule or for the Calendar.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. 

Calendar Deployment

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.

 

Display children header