DSXchange

I don't work with DB2 but from the forums here I think the DB2 stage wants dates in internal format, so you might try just the IConv part.

Trouble is, this is all about the DataStage function so how it works "in general" is pretty much irrelevant, I'm afraid.

That's the first time I've heard that comment. Interesting. I have not found that to be true in my usage of it, but perhaps there are things I didn't review during several projects in the past several years using MapStage in combination with WTX or using WTX with RTI, which was supported in release...

LMFAO

DEBUG? What dat do?

In other words, never seen it before and never used it. Wondering how much it is contributing to your issue... perhaps that is the sum total of it.

Not according to the error you posted. Perhaps your issue is now coming from elsewhere in the job, target rather than source side?

OK... your filename ends in ".fs" which is for a fileset but it found a dataset where it pointed to instead. Any idea how that happened? Naming collision?

You really should start your own thread for something like this.

I've never seen the "MOUNTED" one mentioned before and have no idea what it means or does. What happens if you remove it from the job?

Where is this hashed file or any sort of reject link / mechanism in the diagram you posted? How exactly are you trying to do this?

Not even going to guess exactly what you mean by "list of job sequencer", can you try rephrasing the question, please?

There seems to be a disconnect between what the MOD() function actually does and what they want it to do.

You can define it at runtime via schemas.

Is your Googler broken? It's a standard UNIX thing, not a DataStage thing by the way so you can look it up online.

I have zero DB2 experience but let me check a couple of things. What stage are you using? Does it work if your second link has no constraint but instead is simply marked as a 'Reject' link?

You do know that 11g isn't "officially" supported, yes? Unless I've missed something lately. Regardless, have you raised this issue with your official support provider?