DSXchange

Then it would seem your configuration file itself could be the source of the problem, perhaps you should post it? Not sure how much people could help not knowing your topology, but worth a shot.

If the Input file is zero byte none of the record will be uploaded into the database. Rather than saying "none of the record will be uploaded" it would be more correct to note that there is no record to be uploaded. Another option - check the file size before processing it. When it has da...

True... the WFF stage with a wait time of zero simply does an existence check.

How about we ask this question in the proper forum?

<moved>

First off your "$file" is a relative path and I suspect you meant to use an absolute one - i.e. one that starts with a slash. Never mind that you technically should pass the path to the file as an argument and then set file=$1 and lastly pass back a status like 0 or a 1 rather than just th...

Not that I know anything with any degree of certainty but I don't believe the current site will be changing. As in ever. From what I recall, there have been plans in the works for a new version of the site but no idea what ever became (or will become) of that. Perhaps there. Or here. Who the heck kn...

Seems like you should enable the Exclude Partition String property.

<moved to the Server forum>

There's no Copy stage in Server jobs, other than that - correct.

(sigh)

Moved.

You haven't stated what your join criteria is. I'm guessing that if your date is part of it then you could consider a join failure to mean "not equal". Otherwise, yes... simply compare them in a transformer. Is all you need to know is if they are equal or not equal? If so, then the string ...

Either make sure they're all in the same string format or convert them to a date first. StringToDate() comes to mind for the latter. After that, just... compare them.

arvind_ds wrote:Don't know why it is behaving differently at different times.

Involve your SysAdmin. What flavor of UNIX is this, by the way? Wondering if you have some kind of a journaled filesystem, I've seen behavior similar to that with them before...

Yeah, yeah, whatever.

To round this out, there are several "log" functions available as part of dsjob so best to read the documentation on the Command Line Interface.