How you call the job, is it through the sequnce or from command prompt. If the job is been called from command prompt by dsjob command, you can make use of 'dsjob -run -warn # {job name}' property. You can provide the warning limit at the -warn parameter.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
I need information as well. Can anybody please suggest a way to set number of warnings for individual jobs, rather than for all the jobs when using a sequence?
If by that you mean running a series of jobs via a Sequencer and you want individual jobs to have different 'Abort after' warnings levels - you can't. That kind of thing would require custom job control code.
-craig
"You can never have too many knives" -- Logan Nine Fingers
OK, that would mean if the previous poster 'Aim High' were to set warning limit to 50 for his dimensions and 1 for the Fact, then he would need to have them in separate sequence. Am I right?
I am planning to force abort a job after 50 errors . Is this possible by writing a code in a job. i.e by capturing number of rejected rows and then force abort a job. How can i do this in a simple way. I need to incorporate this in so many jobs.
nkln@you wrote:I am planning to force abort a job after 50 errors . Is this possible by writing a code in a job. i.e by capturing number of rejected rows and then force abort a job. How can i do this in a simple way. I need to incorporate this in so many jobs.
Based on the number of reject rows you can abort by UtilityAborttoLog() routine.
If it is based on number of warning, when you start the sequecne set your warning limit to 50, datastage it self will abort the job after this.
I dont think you can do that at the job level. Forcing a job to abort inside the job, never heard of it, and cant think of any way to do it.
As others have suggested, you can
a) Do it via sequencers or
b) By custom job routine.
Gurus, Can this be done by building a Batch job outof these jobs and in the job control,
add a code
DSguru2B wrote:I dont think you can do that at the job level. Forcing a job to abort inside the job, never heard of it, and cant think of any way to do it.
It's a propery of every constraint. You can change the 'Abort after' value from zero rows (which means never) to a specific number - and when that many rows have gone down that link, the job will abort.
-craig
"You can never have too many knives" -- Logan Nine Fingers