DSXchange

I'm fairly certain that that has been reported as a bug here.

Me, I'd just cat all the files together then bulk load. Once.

Depending on your skill level, you could build a looping Sequence that doesn't wait for each job so that (eventually) they will all be running in parallel, but then you may end up with locking and/or resource problems.

Close. The MONTH.LAST transform returns an internal date and expects the input as YYYY-MM. But you are correct that you can compare a date to this date and see if they match, as long as you've prepared both properly.

Then it seems that you should open a case with your official support provider, ask them how to resolve this.

In other words, you can't. So don't check to see if the file was created, check to see if rows were written to it. DSGetLinkInfo w/ DSJ.LINKROWCNT is one common way.

What about DataStage? You can certainly create 'bad' and 'discard' files if you like.

Constraint?

True. Our primary sources here do a less than stellar job of enforcing their own dang rules, so generally we get to do that.

I think if a data file is extracted from a database and loaded into DataStage then the explicit validation of every field is going overboard. If no transformation happens between the database table and the CSV file it is unlikely contain data that doesn't match the metadata of the source table. To ...

Not to mention the fact that proper naming and use of stage variables, which your post seems to exemplify, goes a long ways towards self-documenting the logic. As Ray notes, the jobs I've seen where constraints are huge collections of expressions fill one with dread at the prospect of having to main...

So you found the culprit, I take it?

You need to double-check because Oracle is telling you that something is too big. I wish it would say what was but it doesn't so you have to find it all on your lonesome.

Cool. :D

You haven't stated your problem(s).

As noted, make both 'sides' upper case. While you can do this in the Key Expression for the input, the hashed side will need to be upcased when built. If you need the original case, keep that as an additional data field.