DSXchange

Do you mean to say that if emp.txt has been harcoded, it runs well?

Use the above option to export job wise. You can pass the list of jobs in a category as parameter.

I was looking at the first post.
Still you can use between both side of the Aggregator.

Pre sort is not really need for Server job aggregator. (Unless specified in sort option otherwise).
mutex - The lock held amog the process. Try to use IPC stage between two aggregator stage.

Cleanup Resource option available in Directore might help you to track the user (PIC) accessing that particular job.

*'s also apear if you dont get a match (join) in the two input record set, and as a result nullify the date field. Which produces the value you got.

IF you perform a lookup, yes there will be certainly diference in performance. The one used for reference should be less in number when compared to the main steram. But not in join stage as for as I know.
May I know what is the case of Informatica?

Have you found the reason why it is available in SQL?

You can check in ./Ascential/DataStage/PXEngine.
But the file available under the directory you serach should also not be with 0KB

No such comparison is officially give atlest for join stage.

Say you have four nodes. And the data for the first join be, key1 key2 key3 key4 key5 w x y z 1 w x y z 2 w x y z 3 w x y z 4 If you make hash partition on all the 5 keys, each record will go into each partion (most probably). If you make hash partiton on first four records all the above four recod ...

Null Field Value or Null Field Length should match the given length of the field.

HI and welcome aboard :D
Are you sure you found the file under /home/dsadm/Ascential/DataStage/PXEngine?

Oh ya....
This is what results, if the post is not posted on correct forum.

Welcome Aboard :D
Is the job holding Folder stage is ahead or behind the WaitforFile activity?