...
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
| Info | ||
|---|---|---|
| ||
Run-times set for an object in the JOC Cockpit are intended as temporary - i.e. as additional to settings to those configured with JOE or a text editor and which are saved on the file system. RunRun-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. This means that they will not be shown : they are not visible in the JobScheduler Object Editor, JOE and cannot be edited in JOE.However, they will 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.
...