So we have a Autosys job (let's say JobA) that's stuck in a loop due to the condition NotRunning (jobA). So, the job continuously restarting itself, moving from STARTING state to RUNNING state, completing either in SU or FA & restarting itself.
To support the look-back feature, you must add an additional operand to the condition statement. You can apply the look-back feature to job status, cross-instance or external dependency job status, and exit code condition types only. You cannot apply it to the global variable condition type.
i want to use if else statement in OGNL scenario: i have 3 input parameters .i have to run an action for 3rd input with help of input 1 and input 2. i have to pass input 1 or input 2 to the action item which is added in input 3. kindly help me with ONGL expression to get the desired output.
When i am studying the look back condition, its taking the last instance run of the condition or predecessor job.Just want to know when to use this look back co
Hi there, FYI, I am new to autosys. I am trying to use success (job_a, 01.00) condition, which I believe according to docs check if job_a is successsfull within the last hour or not right? But in autosys workload automation. It is always showing condtion not satisfied. May I know why? Does it depends on any other things. I tested it by manually changing the status of job_a to Success. But in ...
vRA 8 YAML Dynamic Condition Evaluation Phil Kauffman Aug 29, 2022 09:20 PM Hello, We have distributed datacenters and we use different customization specs based on location and ... 1. vRA 8 YAML Dynamic Condition Evaluation
condition: f (job1, 00.10) | f (job-r,00.10) alarm_if_fail: 1 Both jobs run the same command. job-1 runs at 1am if it succeeds, great, we're done. Then starting at 1:10 job-r will evaluate starting conditions and run if job-1 failed or moving forward through the start_times if job-r failed during that time period. Hope this helps. Regards, Mark ...
