Introduction
The JOC Cockpit Run-time Editor has been introduced to simplify making temporary changes to Job and Order start times by adding Run-Times or selecting Schedules. When editing Run-Times the editor follows configuration terms such as, "Execute an Order every Monday at 09:00" or "Execute a Job every 1st and 2nd Monday of the month".
Relation between Run-Times and Schedules
Jobs and Orders can either be started using the JOC Cockpit according to Run-Times or Schedules but not both:
- Run-Times are Job or Order-specific - i.e. they are properties of a particular job or order.
- Schedules are specified independently of the Jobs or Orders they are used for and can therefore be more used flexibly and more efficiently, particularly in environments where there are large numbers of Jobs and Orders that run regularly.
The JOC Cockpit Run-Time Editor can be used to configure Run-Times and specify Schedules but selection of a Schedule for a Job or Order that already has a Run-Time - as shown in the screenshot below - will cause the run-time to be deleted and vice-versa.
Configuring Run-Times
Caution
- Run-times set for an object in the JOC Cockpit are intended as temporary configuration that overrides configurations saved on the file system.
- Run-times set for an object in the JOC Cockpit are not written to the file system but are saved in the JobScheduler's own memory: they are not visible on the file system.
- Run-times set for an object in the JOC Cockpit are persistent - they remain active after a restart of the JobScheduler.
- They can be overwritten by changes to files on the file system.
Configuration
The following screenshots show the main configuration panels available for the Run-time Editor.
Setting up a Schedule valid for a limited period of time:
Configuring a Schedule to run for a specific month:
Configuring a Schedule to run on specific days of the week:
