DSXchange

Change your mindset about what "Key" means. In the WHERE clause of a SELECT statement, "Key" means "search key", rather than "primary key".

Could it be that someone has run VERIFY.SQL SCHEMA pathname over the project, which might put the empty schema entries into the hashed files?

Not from DataStage, as far as I am aware, unless you create your own encryption routines.

UniVerse was acquired from IBM by Rocket Software on 01 Oct 2009. The IBM web site redirects you to the Rocket Software website, where the manuals can be found under the Resources tab there.

Moderator: please move to parallel forum

The answer is vastly different depending on job type.

When's the interview?

Command stage is executed for every row.

There are other analogies. I like that of the toll collector. Most of the time doing nothing but, when something comes along performs a small amount of processing (collecting the toll, maybe issuing a receipt) then, once that transaction has ended, going back to doing nothing till the next one comes...

The limit on the qualified job name (that is, the job name, the dot and the invocation ID) is the limit on your hashed file key size. Typically this is 768 bytes.

When I first saw Rocket Software in the U2 announcement, I immediatly thought of Bullwinkle J Moose (aka Mr Know-It-All) for some reason.

QualityStage stages are just DataStage stages in version 8, so you'll need to look more carefully. Find one by name, and then discern its OLETYPE etc. I may have been wrong with "quality" and/or the directory may not be in the project - I can't check this this week. Is there a subdirectory...

This forum is for questions about QualityStage.

Yours is not.

Please post your question in the appropriate forum, namely the DataStage Enterprise Edition forum.

Akumar1 wrote:I have an urgent issue.

DSXchange is an all-volunteer site whose members post as and when they can. We don't do "urgent".

If you need urgent answers, sign up with your official support provider for premium service. Learn the true cost of "urgent".

Are you using an Oracle Enterprise stage? Are you capturing the rejected rows using a reject link? If so, push these rows into some structure (maybe a text file) that you can review with a hex editor.

And you CAN change environment variable values in production.