Warnings without abort causes non restartability

moose2079 · Post by **moose2079** » Mon Sep 08, 2008 9:09 pm

Hi there,
We have a master sequence that aborts when a child datastage job gives warnings. This is what we want but the master sequence is no longer restartable - it must be rerun.
Reason is our master sequence is only restartable if a child sequence aborts or a child datastage job aborts.

In this case the datastage job is directly run by the master sequence - as no child job or child seq aborted the master sequence is not restartable

The only way around this problem that I can see is creating one child sequence to run this one datastage job, and set the child sequence to abort if any warning messages are created by the datasatge job

My question is:
Is there a way to force a datastage job to abort if it has any warning messages?
- ie without creating a sequence to run the datastage job?

chulett · Post by **chulett** » Mon Sep 08, 2008 9:51 pm

Depending on what exactly is generating the warnings, there are several ways.

Typically one would set the warning limit when the job runs to a (very) low value. You can also create a reject link set to 'Abort after X rows', set X to 1 and send bad things down that link. One bad thing and the job aborts. Or a routine can be called when problems occur that calls the DSLogFatal routine. Heck, you could even create an after-job subroutine that checks the JOBINTERIMSTATUS and aborts the job if it determines that the job was going to complete with warnings.

Multiple ways.