DSXchange

Is your hashed file lookup set up properly? Are you certain you've set up both Column1 and Column2 as keys in the hashed file so both are passed to the hashed file from the transformer and used for the join?

Please note the option / check box to only run on job success.

So... resolved?

Interesting... back when I searched for this error message found several sites with information like this, hence my comment.

Interesting, didn't consider that this might be a lookup. My response was based on your rather sparse post making me think this was the source in your job.

Or what Shane said.

You'd need to build the string before the job starts and pass it in as a parameter. That or build the entire SELECT in a file and have the stage use that file.

While the DataStage TX product (formerly Mercator) would have automated that for you, I don't see why not. It's just a file after all.

The ones listed in the Install & Configuration Guide.

Since you noted this is a Parallel job, let's get you in the proper forum... done.

Then it would seem that you'll need to upgrade to a non-free / open source version of the database.

You obviously have a resource issue... but what exact resource I can't say but I'd double-check your kernel parameters. First thought - run fewer jobs at the same time. Regardless of settings, resources are not infinite.

hsahay wrote:Regardless - unless the default of 50 is hard coded deep inside the datastage code and is unreachable to us somebody should be able to tell me where to find it and how to change it. sigh !!!

That somebody would be IBM Support.

I think this is just one more example in a long line of examples of bugs / issues in the old versions that have since been corrected in newer releases. And you are in a long line of people who were (unknowingly) reliant on those bugs.

Or reducing the number of warnings the jobs produce?

I edited my post to include more information probably just as you were replying.