Abort after 50 Warnings with no limit

[Pierre]

Hi,

I have a problem since a couple of days :

My project is set to "no limit" on Warnings.
Since yesterday, 2 different jobs aborted with error "Aborted after 50 warnings".
Those 2 jobs are launched by a Control Job, with no DSSetJobLimit, and I don't see any other way to set an limit on a job...

Does anyone have an idea about what's happening ?

Thanks in advance.

[priyadarshikunal]

I think 50 is the default value for warning limit. does the control job sets it to unlimited (0) ?

[Pierre]

Hi, priyadarshikunal

50 is the default, but it is set to unlimited for my project.

Just to make it clear, all jobs in this project are started by Job Controls, themselves started by another scheduled Job Control (no manual interventions).

I searched in all Job Controls, there is nowhere DSSetJobLimit specified, so the limit shouls be the one of the project (0).

[J.Calvo]

Open Director,
In the Menu Bar select Tools > Options > Limits >
The window have two parts, Warnings and Rows, In Warnings is selected really NO LIMITS ?

[Pierre]

Yes, really !

[Pierre]

Yes, really !

[priyadarshikunal]

50 is the default, but it is set to unlimited for my project.

I don't think you can set it to unlimited for the project. The setting in director is only for the jobs triggered from director. And its a client setting which doesn't affect the project.

Just to make it clear, all jobs in this project are started by Job Controls, themselves started by another scheduled Job Control (no manual interventions).

check the trigger, if the dsjob was triggered with -warn 0 (if used) else check trigger script/enterprise scheduler for the setting.

I searched in all Job Controls, there is nowhere DSSetJobLimit specified, so the limit shouls be the one of the project (0).

read my first statement of this post.

[chulett]

There is no such thing as a Project level warning limit. You can set it as a default for your Director client but that just affects jobs you run manually. Otherwise, unless specifically overridden, the default is 50.

[ray.wurlod]

Were these jobs started from dsjob command with no -warn option?

[Pierre]

The problem is resolved.

The jobs were started by Job Controls.
In fact, the limit was 50 warnings at job run level.

Thanks to all for help.

Pierre.

[caterin_huang]

The problem is resolved.

The jobs were started by Job Controls.
In fact, the limit was 50 warnings at job run level.

Thanks to all for help.

Pierre.

Dear all,
I had the same problem as what Pierre get. But I can't find how to set the limit warning at job run level. Can anyone help me? For your Information, I'm using Datastage 8.1

Need help so much..

Thanks in advance,
Caterin

[chulett]

If by "job run level" you mean "dsjob from the command line" then you need to use the -warn option as noted in this thread. Running from the Director you will have a Limits tab where that can be set.

[caterin_huang]

If by "job run level" you mean "dsjob from the command line" then you need to use the -warn option as noted in this thread. Running from the Director you will have a Limits tab where tha ...

unfortunately it is not triggered from the command line. but triggered using sequence. is there somewhere in the sequence we should set the limit warning?

Thanks in advance,
Caterin

[chulett]

If by "job run level" you mean "dsjob from the command line" then you need to use the -warn option as noted in this thread. Running from the Director you will have a Limits tab where tha ...

unfortunately it is not triggered from the command line. but triggered using sequence. is there somewhere in the sequence we should set the limit warning?

Discussed here. Anyone wanting to chime in, please do so over there. Thanks.