I have a requirement where I need to abort the following job based on a value written to a file using writeu in a routine, in the current job. To achieve this, I need to manually set the Jobstatus of the current job to aborted, so that my next job in the sequence does not get kicked off.
Job1 -----> Job2 -----> Job3
Based on the value written to a file in Job1, I need to manually set the Jobstatus of Job1 to Aborted, so that Job2 does not get kicked off
pnchowdary wrote:I need to manually set the Jobstatus of the current job to aborted
You can't manually set it, so put that approach out of your head.
What you can do is build a routine to read the file which you can execute via the Routine Activity stage between the two jobs. Abort the routine (ie, call DSLogFatal) if you don't like what it reads. Triggers handle the rest.
Why not just do the abort in the original routine?
-craig
"You can never have too many knives" -- Logan Nine Fingers
You can still exert total control over the sequence using specific values written to files (as you propose), without the need to abort. Use custom triggers and/or Nested Condition activities to control the flow of execution.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.