poorna_76 wrote:Now since i am running the job through Sequence, i don't have control to set the job limit.
Sure you do... or at least you should. If you run the Sequence job itself with a Warning Limit of 1 it should pass that limit to all child jobs it runs automatically. As noted, it's supposed to be as easy as that.
Thanks chulett. It worked. All child jobs were passed that warning limit 1.
Since the operator may not always run the Sequence , by changing warning limit to 1.
I am looking for the Sequence to take care of this inside by itself.
A script or 'wrapper' process that uses dsjob to run the job rather than using the Director to run it. That script can have the "-warn 1" in its command line to enforce that rule.
The only other way would be to change the default in the Director so that it defaults to aborting after 1 warning, but that would effect all jobs run that way.
Otherwise, the process will have to include a step to switch to the Limits tab and set the Limit to 1 before they click the Run button.
-craig
"You can never have too many knives" -- Logan Nine Fingers
chulett wrote:A script or 'wrapper' process that uses dsjob to run the job rather than using the Director to run it. That script can have the "-warn 1" in its command line to enforce that rule.
The only other way would be to change the default in the Director so that it defaults to aborting after 1 warning, but that would effect all jobs run that way.
Otherwise, the process will have to include a step to switch to the Limits tab and set the Limit to 1 before they click the Run button.
Thanks chulett.
What is the best way to change the default in the Director so that it defaults to aborting after 1 warning.