DSXchange

I don't believe so.

I'm wondering... why run another job from 'after-job'? That's not something I've ever considered doing and am wondering why you would have set things up like that. If you don't mind.

No, not anybody... just you.

Please don't jump on the end of an old post and say "me too!". Start a new post, give us your particulars and explain your job design and errors. Then maybe someone would be able to actually help.

My personal opinion is you can't get "decent performance" from either of those combo Actions. And from what I recall from reading here, the DB2 stage not only logs a warning when your Array Size is greater than 1 with either of those actions, but it actually changes it to use 1 during the job run. P...

However, just now noticing the forum we're in, I'll add the caveat that in my specific case we are Server only. Not sure it matters, but wanted to make that point.

We support both 9i and 10g using a 9i client without issue.

cd to $DSHOME and source the dsenv file file to ensure all your environment variables and search paths are properly set:


Then run your job.

roy wrote:By definition an empty fie should contain nothing if it is really empty

Or it could contain a single header record. That's why, IMHO, you should check the LinkRowCount and not the file size as that will 'always' work for you.

Prevent? No. If it really bothers you, you can build an after-job subroutine to detect the empty file and delete it if you like.

Your job design is fine, but I'd guess your metadata is wrong. I'm forced to guess because all you've told us is you "get a warning". It would be really swell if you'd share the actual warning with us. And take that warning and try to figure out what is wrong with the way you've defined the file in ...

You should be able to Search here for 'range lookup' and find several conversations on this topic.

Not with that much information to work with.

Would need a better idea of your job design and what errors or warnings you received. Can you do a 'View Data' on the input file?

So... like this?

The OCI stage has similar issues. It will still capture rejects but if the Array Size is not equal to 1 it will capture the wrong information. From what I recall, the docs specifically say to set it to 1 for proper reject row capturing. Note this is specifically in regards to capturing physical reje...

Granted. But no-one has explained the 'how to ask' part. Me, I'd still stick with going over and banging my SA on the head, ask them what version is installed.

However, all that does is find it. The question is how to determine the compiler version.