Page History

Known Issue Status

Behavior

• Passed Test Case
  • Starting Situation
    • A holidays.xml file is being included into a from a live_file folder into an order for "non working days"
    •  order.xml and holiday.xml  are deploy in to the JobschedulerJobScheduler
    • Jobscheduler read JobScheduler reads the order.xml and included file holidays.xml 
    • Jobscheduler JobScheduler suppress the job execution for dates defined as "non working days" in the holidays.xml
  • Action
    • Check JOC and right click on the order --> show start times --> submit
  • Behavior
    • Jobscheduler JobScheduler will show all dates jobs will be executed. Jobscheduler JobScheduler will supress execution for "non working days"
• Failed Test Case
  • Starting Situation
    • A holidays.xml file is being included into a from a live_file folder into an order for "non working days"
    • User apply changes into The user applies changes to the holiday.xml file and deploy deploys it in to JobschedulerJobScheduler.
    • Jobscheduler JobScheduler does not read CHANGES changes from the  holidayholiday.xml file.
  • Action
    • Check JOC and right click on the order --> show start times --> submit
  • Behavior
    • The Jobscheduler JobScheduler will ignore the changes from holiday.xml file and will execute jobs on "not working days".
• Explanation
  • Jobscheduler read JobScheduler reads new or and changed job, job chain, order and schedule files as soon as they are deployed in the Jobscheduler JobScheduler live folder. Jobscheduler JobScheduler does not reload chnages changes done in the  included  files included holiday files i.e. holidays.xml.

Requirement

• The order should consider a newly added job node at the top of the job chain and should execute accordingly JobScheduler should auto reload changes effected to the included holidays.xml file if configured from a live_file attribute.

Workaround

• Solution 1:  Update the order configuration
  • An updated order configuration file will force JobScheduler to reload the order configuration and to adjust the assignment of the initial state.
• Solution 2: Use start and end nodes
  • We recommend that you use our /sos/jitl/JobChainStart start job as the first node in every job chain and our /sos/jitl/JobChainEnd end job as the last full node. These are dummy jobs without any function of their own. However, they are helpful for fixing orders or pre-/post-processing rules: changes to the names and/or order of states within a job chain do not require a change to the order.

...

•  Restart JobScheduler
  • from JOC Menu
  • from command line $SCHEDULER_HOME/bin/jobscheduler.[cmd/sh] restart
• Solution 2: Reload job configuration
  • update all the orders using a system command i.e. Linux touch command  touch $(grep -Rl 'bank-holidays.xml' *.order.xml)