DSXchange

Welcome aboard.

You really haven't given enough information - I am presuming that your question refers to a Lookup stage.

The answer is "maybe". On the output link of the stage you can control which input columns get mapped to output columns.

Just set the Hashed File stage properties to "clear file before writing". It doesn't matter where the hashed file is. If the stage can write to the hashed file, it can clear it. (And it will use CLEAR.FILE technology under the covers.)

Hard to say with so little information. Is the NLS map actually loading when DataStage starts?

At least (m+2).

And yet it is so easy to obtain a premium membership, which will allow you to read entire premium posts, as well as gaining other advantages.

Remove Duplicates stage keyed on "id" retaining the First record from each group.

Probably not, though you may need to set some environment variable(s) that your database client software needs. Your DBA should be able to advise on this.

How many machines is DataStage running on?

One solution is:

Then try reading it as CAST (column AS VARCHAR2) and handling the variants within DataStage.

Remember that the first record is number 0. So record 27 is the twenty-eighth record in the file. Offset 0 is the beginning of the file, and the first character of your file in that line is {0d} - that is, a line feed character.

So put the "trim the trailing comma" logic into the first job.

Yes, but that doesn't give you a third format.

The log that you read is whichever one the current job handle relates to. You must control this in your code. You can use functions like DSGetJobInfo() with DSJ.JOBCONTROLLER to determine the parent sequence's name.

These counts are close. Have you created any custom stages?

Moderator: please move to Enterprise Edition (parallel) forum

This is not a QualityStage question.