reject link creates a file

uzl · Post by **uzl** » Fri Mar 08, 2013 6:29 am

I'm implementing jobs that check datainconsistenties between tables. For example : I check if all instanties of a column in one table also exist in another table. I use a lookup-stage for this. The reject link creates a file with all the inconsistenties. However, when no record is rejected, an (empthy) file is created. How can I avoid this ?

chulett · Post by **chulett** » Fri Mar 08, 2013 8:04 am

You can't.

uzl · Post by **uzl** » Fri Mar 08, 2013 8:43 am

not the answer I was hoping for but thanks anyhow

prasannakumarkk · Post by **prasannakumarkk** » Fri Mar 08, 2013 8:44 am

delete empty files in after job subroutines.

chulett · Post by **chulett** » Fri Mar 08, 2013 8:58 am

Was thinking about my answer and realized it was a little... terse. So for grins, here's the longer explanation:

When a job starts, all target stages are opened / initialized. It is at that time that they do whatever they need to do to "get ready". A database stage connects to the database, a file stage creates the file if it doesn't already exist, etc etc. None of those things are conditional, meaning they don't wait for the first row to arrive before they happen.

As noted, if that really bothers you the file can be checked "after job" and deleted if found to be empty.

prasannakumarkk · Post by **prasannakumarkk** » Fri Mar 08, 2013 9:19 am

thanks craig for the information. I always wondered why it happened.

ray.wurlod · Post by **ray.wurlod** » Fri Mar 08, 2013 7:26 pm

Discover such instances using cross-able analysis in Information Analyzer.