Abort the Sequence as soon as job logs 1 warning

poorna_76 · Post by **poorna_76** » Wed Aug 30, 2006 10:51 am

chulett wrote:
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.

Any more thoughts?

Thanks in Advance.

chulett · Post by **chulett** » Wed Aug 30, 2006 10:59 am

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.

poorna_76 · Post by **poorna_76** » Wed Aug 30, 2006 11:07 am

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.

Thanks in Advance.

chulett · Post by **chulett** » Wed Aug 30, 2006 11:10 am

Director: Tools / Options / Limits - set it there. Keep in mind that this is not a global setting, but is a per user setting.

poorna_76 · Post by **poorna_76** » Wed Aug 30, 2006 12:01 pm

chulett wrote:Director: Tools / Options / Limits - set it there. Keep in mind that this is not a global setting, but is a per user setting.

In was asking with respest to the global setting. Anything in DataStage Administrator .. or some where else..

Thanks in Advance.

chulett · Post by **chulett** » Wed Aug 30, 2006 12:05 pm

No such beastie or I would have mentioned it.

meena · Post by **meena** » Wed Aug 30, 2006 12:06 pm

Hi poorna,
I think it is not possible to set gobally

In was asking with respest to the global setting. Anything in DataStage Administrator .. or some where else..

ray.wurlod · Post by **ray.wurlod** » Wed Aug 30, 2006 6:36 pm

Only four posts back on this very thread:

Director: Tools / Options / Limits - set it there. Keep in mind that this is not a global setting, but is a per user setting.

But it's applicable to every job started by the user, so it's fairly close to global.

chulett · Post by **chulett** » Wed Aug 30, 2006 8:41 pm

And saying 'per user' is a little bit of a misnomer - it would have been more proper for me to say per installation of the Director.

poorna_76 · Post by **poorna_76** » Thu Aug 31, 2006 7:37 am

chulett wrote:And saying 'per user' is a little bit of a misnomer - it would have been more proper for me to say per installation of the Director.

Thanks chulett.