Versions Compared

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 changing Job and Order run-times and is intended to follow natural language making temporary changes to Job and Order start times by adding Run-Times or selecting Schedules. When editing Run-Times the editor follows configuration terms such as, "Execute a order an Order every Monday at 09:00" or execute "Execute a job Job every 1st and 2nd Monday of the month".

Relation between 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 Order or orderstandalone Job.
  • 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.

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