Setting warning limit override at job

saikrishna · Post by **saikrishna** » Thu Dec 04, 2008 5:16 am

Hi

I have a master sequencer which calls five jobs in a sequential order.

While running the master sequencer, i have given 50 warnings limit...which defaultly applies to all of the five called jobs.

But, I would like to override this 50 warning limit with a 100 warning limit for only one job out of five called jobs whenever there is a master sequence runs with 50 warning limit globally.

Is it possible to do this in DataStage?

Thanks
Sai

Pierre · Post by **Pierre** » Thu Dec 04, 2008 5:31 am

You can use a job control to launch your jobs, using the following :

...
NumberWarnings=50
NbWarnings = DSSetJobLimit(JobHandle, DSJ.LIMITWARN, NumberWarnings)
ErrExec = DSRunJob(JobHandle, DSJ.RUNNORMAL)
...

to parameter the abort of jobs after warnings.

Pierre.

saikrishna · Post by **saikrishna** » Thu Dec 04, 2008 5:51 am

Can I use the existing job control routine that was generated by datastage itself?...means the "master sequencer" that i built...can i use this and change its job control routine for warnings?

Pierre · Post by **Pierre** » Thu Dec 04, 2008 7:26 am

I think the code generated by DataStage is read-only...

Pierre.

Mike · Post by **Mike** » Thu Dec 04, 2008 7:41 am

Why not fix the job so that it doesn't generate warnings?

I'm firmly in the camp that believes the warning limit should be 1. In my opinion, using the default warning limit of 50 is just lazy programming/design.

And it's downright dangerous... what if you get a warning that actually requires you to take some corrective action to avoid corrupting your data warehouse? If you allow any warnings, there's a good possibility that you're going to miss the important ones.

Mike

Pierre · Post by **Pierre** » Thu Dec 04, 2008 7:55 am

Mike is right, but sometimes we receive files with special characters which have to be rejected.
I sometimes use jobs with no limits (only during the running time) with a reject file to store the warnings, so I can run the job and treat the rejects later.

Pierre.

chulett · Post by **chulett** » Thu Dec 04, 2008 8:04 am

You can't use the Job Activity stage for this. You'll either need a Routine that uses DSExecute and DSSetJobLimit or a script via Execute Command with dsjob and "-warn 100" to run the job.