Andreas

Maybe it's not immediately evident. Create a Non-working Day Calendar as from the attached calendar.png screenshot that specifies every Second Tuesday of Month. Create a Schedule that makes use of an All Days Working Day Calendar (365 days) and that adds the above Non-working Day Calendar adds a restriction for Second Tuesday of Month adds a rule for execution on non-working days: "after non-working day" to its period See attached screenshots.

This is fixed.

Hi Chico, I cannot identify any reason to assume that the behavior is related to the JS7 Agent. If your job calls an external .ksh script, then there is no caching mechanism in place with the Agent. In fact, the job script is cached in the Agent's <agent-data>/work/scripts directory as the job script has not been changed. The Agent will start a new process and will run sh -c <agent-data>/work/scripts/job-script.sh Please, check if you find a caching mechanism from the file system. If an order is...

Hi Chico, you have a spelling error in your confirugration. job1 echo "DATE_TRT=${date_trt}" >> ${JS7_RETURN_VALUES} This means you create the dynamic workflow variable DATE_TRT in uppercase letters. job2 it has an assigned evironnment variable DATE_TRT = $date_trt This means you assign the lowercase variable name date_trt. Make the variable name uppercase as used in job1 to make this work.

Hi Chico, the JS7 - How to pass variables to subsequent jobs article explains how to achieve this.

Hi Patrice, sorry, your post slipped our attention. Job Resource variables are provided as environment variables for Shell jobs. For JVM jobs such as JITL jobs the arguments of a Job Resource are used. The YADE XML configuration makes use of both: if invoked from a Shell job, then environment variables are substituted. When invoked from its JITL job, then arguments are used. In both situations the syntax is the same: ${variable}. Please, consider correct spelling. BTW: in your Job Resource, you can...

Hi Chico, sudo works for a single command when used in scripts. This is a shell limitation and is not related to JS7. Your job script should use multiline input like this: sudo -su anotherone <<EOF whoami pwd EOF A practical approach is use of JS7 - Script Includes to hide sudo commands from job scripts: ##!include sudo-begin pwd whoami sleep 30 ##!include sudo-end The sudo-begin Script Include holds the line: sudo -su anotherone <<EOF The sudo-end Script Include holds the line: EOF

JS7 JobScheduler LTS Release 2.8.2 available