DSXchange

Various options: 1. SQL Join: If it is equi join select a.rowid,data_load_insert,data_load_update from tablea a,tableb b where a.rowid=b.rowid If it is full outer join select a.rowid,data_load_insert,data_load_update from tablea a full outer join tableb b on where a.rowid=b.rowid 2. Use lookup for j...

No, don't think it is possible from within the transformer, if the transformer is just following the Sequential file stage. Introduce one more stage in between (may be an IPC) (and try DSGetLinkInfo to get the processed row counts and call the routine to get the value to be written to the target tab...

Are there any separators in between the columns or it is a fixed length file.

You can read the entire row in the file as a column and after that you can process individual columns separately. With such a case you can still have same structure for both of the files.

I am unable to clear it by the clear job log option in director.. The operation hangs and gives some error..

What error it gives, can you please paste it over here.

BTW loveojha2, can you tell (tips) how do you conclude/frame this commands? I learnt it on this site only, and at the same time, DS_ROUTINES stores info about name, desc, etc of the routines and it is too a Hashed File, moreover by issuing LIST.DICT DS_ROUTINES you will be able to see the complete ...

First make it modifyable using then delete it.

Ok.. can you tell me if it is usual for a project with approx 2000 jobs and sequences to occupy 11 GB of space????

We have around 10K maps in one project with around 1 GB of space.

How many jobs are there in the project? If they are not hugh in numbers. My advise could be taking export of the entire project with the executable and creating a different project with that, then you can make a comparison actually, since you have said that you are auto purging the log and you are n...

Do you mean to say that I can DELETE these files?

No
Otherwise you will lose your project

Check which job is 287?
Go to the director of the job and clear the job log, check whether it allows you to clear it or not, if yes, then re run the job.

Check which files are relatively big in size and what is their type (log,RTBP,temp file)?

Just classify the space utilized by the different types of file, that may lead to some clue.

Are there any jobs running with large number of warnings, if yes, then try to modify the jobs in such a way that you don't get warnings at all.

Purge the log files periodically, you can set the options also from the Administrator of auto purge.

Are you using the omit option while logging into the datastage, if yes, try with username/passwd and re compile.

There should be some upper limit on the no of parameters, but should accomodate almost all of the genuine param limit.

More over no limit to the no of character that can be passed (may be 2gb, if there is any).