Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 15

changes.mady.by.user Alan Amos

Saved on

compared with

New Version Current

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minor change to text

...

Excerpt

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 natural language 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 Order or orderstandalone Job.
  • 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.

Anchor
configure-run-times
configure-run-times
Configuring Run-Times

Info
titleCaution
  • 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
  • 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
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.
  • .
  • Run
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.
  • 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.

...

Configuring a Schedule to run on specific days of the week:

 

Deleting Run-times and Schedules

Two functions are available for deleting individual Run-times and deleting Schedules that have been set in the JOC Cockpit:

  • Set Run-time:
    • This function opens a modal window that allows Run-times or Schedules set in the JOC Cockpit to be deleted and new ones configured as required. When all Run-times or Schedules configured for a Job or Order are deleted with this function any Run-time or Schedule configured on the file system will not be (re)activated.
  • Reset Run-time:
    • This function opens a modal window that allows Run-times or Schedules set in the JOC Cockpit to be removed and any Run-time or Schedule configured on the file system to be (re)activated if all the Run-times or Schedules configured in the JOC Cockpit are deleted.

Both functions can be reached from additional Options menus as shown, for example, in the screenshot below, which shows an Order in the Job Chains view:

Image Added

Permissions

The following Permissions are required before all possible changes to Run-times and Schedules can be made:

  • sos:products:joc_cockpit:schedule:change:add_substitute
  • sos:products:joc_cockpit:schedule:change:edit_content
  • sos:products:joc_cockpit:schedule:change:hot_folder
  • sos:products:joc_cockpit:order:change:run_time
  • sos:products:joc_cockpit:job:change:run_time