DSXchange

This is actually not possible in a single query. You need two passes through the data. You can do this with a nested query in the WHERE clause.

While it's true that the Join stage can have more than two input links, they do require a common key, as track_star has pointed out. One solution would be to use two cascaded Join stages; one to join tables A and B, the second to join that result and table C. Or you could use three Join stages: A an...

That would be a good trick! I assume you're not counting the conductor or player process in this, and combining all operators?

Hey, let's totally defeat the functionality of this parallel architecture that we've just spent a squillion dollars on!

"They" are the good folks who manufacture the product.

You had an unexpected network error. An error in your network. Unexpected. It's nothing caused by or due to DataStage, and there's nothing in DataStage that you could have done, or can do, to prevent it. That's not entirely true, you could investigate methods to eschew use of the network. Talk to yo...

You have answered a different question than the one asked.

When you are writing to a sequential file, what partitioning method is mandated?

Wants a second opinion?

Old gag: "Doctor, I'd like to get a second opinion." "OK, I'll tell you again."

Yup.

And it means that MetaStage can't do accurate lineage analysis or where used analysis.

I counsel against using RCP mainly for this reason. Remember, too, that "they" will be coercing you to use MetaStage for all reporting, by deprecating/removing alternatives.

Read through install.sh before proceeding. This will convince you that everything it does is fairly innocuous.

What is Field1? Normally input columns are qualified with their link name. But it could be a stage variable, I guess. Anyway, it needs not to be null for the row to be put out along this link.

In older releases of DataStage, the directory was a stage property and only the file entry name was a link property, so you needed separate Sequential File stages for each separate directory. This is no longer the case. Even so I prefer still to use separate Sequential File stages, because I tend to...

Fire up the Hashed File Calculator on your DataStage CD. It's in the Utilities\Unsupported folder. Play and learn!

If you think about it, the standard lookup in a Transformer stage is a left outer join, in that it returns NULL for every column from the reference input link if the lookup does not succeed.

You typically turn it into an inner join using an output link constraint expression.

I addressed a possible cause of Parameter marker text size exceeds allocated space

Alternative solution.

Do the export with (that is, including) default-valued properties. It's a larger export file, but everything is in it. Then the modification is straightforward.