Introduction
The JOC Cockpit Run-time Editor has been introduced to simplify changing Job and Order run-times and is intended to follow natural language configuration terms such as, "Execute a order every Monday at 09:00 or execute a job every 1st and 2nd Monday of the month".
Run-times and Schedules
Jobs and orders can either be started according to run-time or schedule parameters 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 regularly running jobs and orders. Schedules are configured in the JOE Editor but can be specified for Jobs and Orders in the JOC Cockpit.
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 in the JOC Cockpit will not be shown in the JobScheduler Object Editor, JOE.
The Run-time Editor can be used to modify an existing run-time configuration or to add an additional run-time. For example, consider the situation where an order is to run every day at 12:00, Fridays at 16:00 and at 22:00 on the last day of the month.
- Add Period is used to configure
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:
