Page History

...

• To enable dependency checking the following parameter is added to the order:

  • Name: jobnet_predecessor

  • Value: a comma separated list of job chains that are acting as predecessors of the current job chain. 

  • Explanation:

    • Job chains in this list include the full path to the respective job chain starting from the live folder.
    • Should job chains be renamed or moved to a different location then this parameter value has to be adjusted accordingly.

  • Sample:

    • csijobnet/examples/JobChain_B/job_chain_B specifies a job chain with the name job_chain_B that is located in a folder csijobnet/examples/JobChain_B

Run-Time Behaviour

...

• To enable dependency checking the following parameter is added to the order:

• Name: jobnet_successor

• Value: a comma separated list of job chains that are acting as successors of the current job chain. 

• Explanation:

  • Job chains in this list include the full path to the respective job chain starting from the live folder.
  • When job chains are renamed or moved to a different location then this parameter value has to be adjusted accordingly.
  • see above screenshot for the handling of orders for predecessor checking that shows a parameterization sample.

• Sample:

• csijobnet/examples/JobChain_I/job_chain_I specifies a job chain with the name job_chain_I that is located in a folder csijobnet/examples/JobChain_I

Run-Time Behaviour

...

<?xml version="1.0" encoding="ISO-8859-1"?>

<job  order="yes" stop_on_error="no">
    <script  language="java" java_class_path="" java_class="com.sos.jitl.sync.JobSchedulerSynchronizeJobChainsJSAdapterClass"/>
    <monitor  name="monitor" ordering="1">
        <script  language="javax.script:rhino">
            <include  file="config/live/csisos/dependency/jobnet_check_successor.js"/>
            <include  file="config/live/csisos/dependency/dependency.js"/>
        </script>
    </monitor>
    <run_time />
</job>

...

•  Testing
  • The described behaviour is currently being tested.
•  Exceeded Periods
  • Currently a period spans one day.
  • Due to manual intervention or due to operational problems a period could last longer than one day, e.g. if jobs were delayed and would be executed over midnight or started after midnight. 
•  Multiple Job Networks
  • Awareness for multiple job networks is required. 
•  Repeated Execution
  • Repeated execution should be enabled/disabled by configuration
•  Active Cluster Support
  • This feature relies on the fact that job chains can be stopped to prevent them from being considered as active predecessors. Currently this is not feasible for cluster operation with distributed job chains. The following issues address this limitation and should be resolved with version 1.8:
    
    

    Jira
    server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery key in ( REQ-65, REQ-66 ) serverId 6dc67751-9d67-34cd-985b-194a8cdc9602

    
     
•  Orders without Run-Time
  • Such orders are required to enable the start of an order by the dependency checking Monitor Scripts. 
  • Currently orders without run-time are not considered. Instead, such orders should be identified as empty orders that can be used by the Monitor Scripts to start successor job chains.

...