DSXchange

head -40 should give you first 40lines, tail -40 should give your last 40 lines, apart from this, may I know what difference made your job to run fine?

Still you cannot completly rely on the this performance staticts. The Environmental varialbe Setting in DS Administrator might change this character.

Ok after going through the Operators Guide, though it is given in osh terms, upto my understanding, the auto insertion of partiton and sort happens only if we have auto partition (Datastage). And tsort and psort are the two integrated options of the available Sort stages(Operators). The auto inserti...

Though you dont have any stages that used the temp area aggresively, the parallel execution of the jobs might be the source of you issue.

Kirtikumar wrote:Thanks Vincent!!!

The article is a great help to handle the rejects. In server we used to handle the errors and warnings using link variables.
In PX it is a more time consuming process.

Just wait for few days, you can find another blog for this from the blog-man.

What is the purpose of inactivity timeout parameter that is available in datastage administrator? Does it enforce only on the timeouts only between datastage client and datastage server.

Yes.

Set the value of PWD to your project folder which will be like c:\Ascential\Datastage\Projects\projectname. or just '.' for current directory. Last I can recall, Windows XP is not supported for parallel jobs. Might want to check with the vendor. Not the Home edition but proffesional edition works.

The data sets input to the Join stage must be key partitioned and sorted. is the recomendation given by Ascential, for the best results. Threre is auto insertion of tsort and psort if the data is found not in sorted order. And this can be controlled by the parameter available in DS Admnistrator. Tu...

http://blogs.ittoolbox.com/bi/websphere ... akage-7169

Go thruogh this, you can find the link to exact blog.

Check whether the file is been written under each node pool.
Try to recreate with another set of config file and try to do a lookup.

What is the error you obtained? Parameters are not enclosed with # in routines. For the same reason, I asked you to check whether the value fo parameter is reflected in side routine. Call DsLogInfo("",param_FilePath); If this gives you output value, you can assum parameters can be used inside the ro...

What is the partition used while creating the lookup fileset and what is used while doing a lookup?

You can get these tricks if you go through the blog released by vincent on "Unplesent discharge".
Perhaps what Om Prakash would have suggested you is to check the log file generated by DB2 in its server. That would give more information on teh reason of reject.

It might the obvious myth that gets in to mind that, Partion makes the data sorted. No.

The 100 records in the right will be buffered. Which might not have have crossed you default buffering limit that has been set in DS Admistrator client. Records in the left link will has to be read and should be buffered till it get a first match in the left link. It actually didnt found any match t...