Page 4 of 31. Showing 309 results (0.055 seconds)
How to configure the handling of exit codes by jobs
"/> <period begin="00:00:01" end="24:00"/> </run_time> </job> Without API Set the job attribute stop_on_error to the value no Add command for exit code 1 … store the exit code and change it in accordance with the requirement ./config/live/test/test.sh RC=$? case "$RC" in "0") echo "Script has endedDependency Handling - Program Flowchart
="No"] "Predecessor Order end time" [shape="diamond",fillcolor="limegreen",label="Predecessor Order End Time\nearlier than start time of last\nsuccessful execution date\nfor current order?"] "Predecessor Order end time earlier" [shape="box",fillcolor="palegreen",label="Yes"] "Predecessor Order end time not earlier" [shape="boxJobs
[shape=diamond,label="execution successful?",fillcolor="white"] EndStateSuccess1 [label="End state: success",fillcolor="palegreen"] EndStateError1 [label="End state: error",fillcolor="lightcoral"] Job2_successful [shape=diamond,label="execution successful?",fillcolor="white"] EndStateSuccess2 [label="End stateJob Chains
with single end nodes for success and failure The jobs within the job chain will result in a unique successful end state or otherwise will use the same end state … "] EndStateSuccess [label="End state: success",fillcolor="palegreen"] EndStateError [label="End state: error",fillcolor="lightcoral"] Job1 -> Job1_successfulHow to configure workflow control by return code handling
a job ends in error. In addition, whereas by default a non-zero return code causes the JobScheduler to log an error for the job and to move the order … and 6 and JobChainB has 2 shell jobs. If Job3 in JobChainA ends successfully (i.e. its shell script ends with a return code = 0): .An order will be generatedPowerShell CLI 1.2 - Use Cases - Daily Plan Report
-Null; # start mode mapping $startModes = @{"0"="single start"; "1"="repeat start-start"; "2"="repeat end-start"}; # Dates in local time zone, output includes … ="Planned Start Time"; expression={ Get-Date $_.plannedStartTime }}, ` @{name="Expected End Time"; expression={ GetPowerShell CLI 1.1 - Cmdlets - New-JobSchedulerHolidays
> PARAMETERS Select -Select <String> Specifies the selection of days that is either counted from the begin or from the end of the given interval, e.g. a week, a month, a year: * first: select days to be counted from the begin of the interval * last: select days to be counted from the end of the interval * nextJOC - Basic Functions List
http://www.sos-berlin.com/doc/en/scheduler.doc/xml/modify_job.xml job="jobname" cmd="unstop"/> reread This function is obsolete and removed in the next release. end tasks The end tasks … . Because of this special effect, end tasks, suspend tasks and continue tasks are hidden per default since JobScheduler Release 1.8. You can configureDependency Handling - Documentation
"] "Chain End" [shape="oval",fillcolor="white"] "Chain A" -> "Chain B" "Chain A" -> "Chain C" "Chain A" -> "Chain D" [fontsize="8",label="\l Order A\l … ='jobnet_predeceessor' value='A'/>\l <param name='jobnet_successor' value='E'/>\l </params>\l </order>\l"] "Chain E" -> "Chain End" [fontsize="8JOC Cockpit - Customizations
at 00:00, a week starts on Monday, etc): ±0w means starting on Monday of the current week -3w means starting on the Monday three weeks ago To dates end at the end of a date (i.e. a day ends at 24:00, a week ends on Sunday, etc): ±0M means ending on the last day of the current month +3M means ending