...
| Excerpt |
|---|
The JOC Cockpit Run-time Editor has been introduced to simplify changing Job and Order run-times and schedules and is intended to follow natural language configuration terms such as, "Execute a order every Monday at 09:00" or execute "Execute a job every 1st and 2nd Monday of the month". |
Run-
...
Times and Schedules
Jobs and orders Orders can either be started using the JOC Cockpit according to runRun-time Times or schedule parameters Schedules but not both:
- Run-times Times are job Job or orderOrder-specific - i.e. they are properties of a particular job or order.
- Schedules are specified independently of the jobs Jobs or orders 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.that run regularly.
The JOC Cockpit Run-time Time Editor can be used to configure runRun-times Times and specify schedules Schedules but selection of a schedule Schedule for a job Job or order Order that already has a runRun-time Time - as shown in the screenshot below - will cause the run-time to be deleted and vice-versa.
...
| Info | ||
|---|---|---|
| ||
Run-times set for an object in the JOC Cockpit are intended as temporary - i.e. as additional to settings configured with JOE or a text editor and which are 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 in the JobScheduler Object Editor JOE or a text editor. This means that they can be unknowingly overwritten by an operator or administrator using JOE or a text editor. In addition, changes made to the run-time settings stored on the file system will cause those configured in the JOC Cockpit to be deleted. Note, however, that run-times set for an object in the JOC Cockpit display are persistent - they remain active after a restart of the JobScheduler. |
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.
...
Configuration
The following screenshots show the main configuration panels available for the Run-time Editor.
...