50 warning!!!
Moderators: chulett, rschirm, roy
50 warning!!!
Hi all
I tried search option for this topic and found a lot of help which was almost having the same problem as mine but i just wanted to make things clear as i tried all the changes in my unix code but it is still not working.
Here is my job details...... I have a sequencer which is calling about 10 jobs, now it is presently getting aborted due to the 50 warnings(default),.. I want the whole process to run even if all the records from all the jobs are registered as warning.....
The command that i am using in the unix code is as follows:
"dsjob -run -wait ${ParmList} -jobstatus $ProjName $JobName"
Please tell me where to put -warn 0 option in the command and is it enough to put the -warn 0 option for all the jobs under the sequencer to run without aborting for the 50 warnings condition.
Your help will be appreciated.
I tried search option for this topic and found a lot of help which was almost having the same problem as mine but i just wanted to make things clear as i tried all the changes in my unix code but it is still not working.
Here is my job details...... I have a sequencer which is calling about 10 jobs, now it is presently getting aborted due to the 50 warnings(default),.. I want the whole process to run even if all the records from all the jobs are registered as warning.....
The command that i am using in the unix code is as follows:
"dsjob -run -wait ${ParmList} -jobstatus $ProjName $JobName"
Please tell me where to put -warn 0 option in the command and is it enough to put the -warn 0 option for all the jobs under the sequencer to run without aborting for the 50 warnings condition.
Your help will be appreciated.
Code: Select all
dsjob -run -warn 0 -wait ${ParmList} -jobstatus $ProjName $JobName
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You need to verify that you are actually passing the warning limit correctly to the job run. Echo out the complete dsjob command just before you actually execute it and capture that somewhere.
The documentation says in many places:
After that, suggest you call your Support provider and get an 'official' answer for your particular version and operating system. Perhaps it is a known issue...
The documentation says in many places:
Now, this is all from the 7.x documentation so while I believe it applies to any given version I can't verify that for 6.x. See what you can find in your documentation - check the DSSetJobLimit function as one example.By default a controlled job inherits any row or warning limits from the controlling job.
After that, suggest you call your Support provider and get an 'official' answer for your particular version and operating system. Perhaps it is a known issue...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers