Abort after 50 Warnings with no limit
Moderators: chulett, rschirm, roy
Abort after 50 Warnings with no limit
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.
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.
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
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).
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).
Re: Abort after 50 Warnings with no limit
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 ?
In the Menu Bar select Tools > Options > Limits >
The window have two parts, Warnings and Rows, In Warnings is selected really NO LIMITS ?
Best Regards,
Jorge Calvo
Jorge Calvo
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
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.Pierre wrote: 50 is the default, but it is set to unlimited for my project.
check the trigger, if the dsjob was triggered with -warn 0 (if used) else check trigger script/enterprise scheduler for the setting.Pierre wrote: 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).
read my first statement of this post.Pierre wrote: I searched in all Job Controls, there is nowhere DSSetJobLimit specified, so the limit shouls be the one of the project (0).
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.![Wink :wink:](./images/smilies/icon_wink.gif)
Genius may have its limitations, but stupidity is not thus handicapped.
![Wink :wink:](./images/smilies/icon_wink.gif)
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 48
- Joined: Tue Jan 26, 2010 4:05 am
- Location: Indonesia
Re: Resolved
Dear all,Pierre wrote: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.
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
-
- Participant
- Posts: 48
- Joined: Tue Jan 26, 2010 4:05 am
- Location: Indonesia
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?chulett wrote: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 ...
Thanks in advance,
Caterin
caterin_huang wrote: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?chulett wrote: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 ...
![Exclamation :!:](./images/smilies/icon_exclaim.gif)
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers