DSXchange

You don't have to, but I include it amongst my "best practices" to do so, especially where the early join keys are already sorted.

You need to look at the job score and determine which hashing algorithm was actually used.

Your logic is not clear, particularly If ID > 1 (if this were part of the logic your output would have five rows with ID = 1). Can you please clarify the logic?

Convert() converts one character to one character.

To convert n characters to m characters you need pxEreplace() or, if you have version 9.1, Ereplace().

CREATE.FILE can not be used with a pathname. The filename argument to CREATE.FILE ends up being a VOC entry. If you want to create a pathed hashed file then you need to use the operating system command mkdbfile. Note that this command neither creates nor populates the metadata (dictionary) portion. ...

Use DSGetParam() to retrieve the value from the calling job (job handle DSJ.ME) and DSSetParam() to set it, after DSAttachJob() and before DSRunJob().

Harini, you're off track. You don't need to do this. The answer is encapsulated in my earlier post on this thread.

Probably not, since the post is three and a half years old and not marked as resolved.

However stage variables are not stored in files.

Yes, this was your requirement.

Try

Custom trigger:

Welcome aboard, Gavin

Does a manual refresh (Ctrl+R) in Director correct the status for you?

Then use Arnd's solution. Job start timestamp + @INROWNUM seconds. It will give you exactly what you've specified whether or not you happen to like it.

This is not a pivot problem. This is a "remember the first nine rows in stage variables and use them to populate column1 through column9 while reading all subsequent input lines" problem. Populate the stage variables conditionally on the value of @INROWNUM. Run on a single node or in seque...