DSXchange

I am a bit confused now. Your example is different from your original description. Is your example what you would like, and is the column in both files with the value "1" an added one?

I don't see a performance gain in this scenario, in fact there is a potential for having to re-sort data. If your join left & right streams are sorted and partitioned on the main join key then resorting and repartitioning isn't necessary. In addition, if the data is sorted on one key and not on ...

The software is the same - just branding.

Is this an 8.1 installation and, if yes, have the logs been redirected to xmeta?

I didn't ask you to modify any jobs, just to see if you can create a dummy test job in the new project.

I think that neither of the 2 fixes you did addressed the actual problem that you are seeing. The error message indicates that there is an issue in the xmeta repository and it might be a project-level problem. Can you create a dummy job in the designer in that project and save/compile/run it?

WinSCP is an often used windows application, or you can use the DOS command line "ftp" utility. Another option is to try the browser based ftp mechanism, just type in the "ftp://yourunixcomputer.name.com" url. Every browser has a different way of letting you enter the userid/pass...

DataStage will automatically repartition unless you explicitly tell it otherwise (there are various means of doing this including explicitly setting links or changing default system APT_ variables). If you created a job whith which reads a 2 node dataset and joins it to a 4 node dataset while runnin...

Your reasoning is correct, the calling sequence has noticed the "Warning" status of one or more of the called jobs/sequences.

Data Bytes counts for more than number of columns. You can test your extract by removing most of the columns and seeing if it goes significantly faster.

Replace the hashed file stage with a sequential file stage writing to /dev/null. Is the error still present? Do a reset of the job and see if you have more information in the "...from previous run" entry.

You need to give an absolute path to the OshScript.osh

goutam wrote:export LIBPATH=$APT_ORHHOME/lib:$LIBPATH

should be

I don't know why you think it is bad to call up dssh outside of the $DSHOME directory - I think it is better and safer, as the "UV" account, if inadvertantly modified, can affect all projects on the system. The question regardnig accessing the RT_LOGnnn file(s) in a different project from ...