Introduction
The JOC Cockpit Runtime Editor has been introduced to simplify changing Job and Order runtimes 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".
Runtimes and Schedules
Jobs and orders can either be started according to runtime or schedule parameters but not both:
- Runtimes 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 Runtime Editor can be used to configure runtimes and specify schedules but selection of a schedule for a job or order that already has a runtime - as shown in the screenshot below - will cause the runtime to be deleted and vice-versa.
Configuring Runtimes
Caution
Runtimes set in the JOC Cockpit will not be shown in the JobScheduler Object Editor, JOE.
The Runtime Editor can be used to modify an existing runtime configuration or to add an additional runtime. 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 Runtime 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:
