DSXchange

What sort of thoughts are you interested in? You've explained the customer's setup in detail and it sounds like they have reasons for all of their configuration settings; so whether someone thinks the configuration makes sense or not won't make a difference. What kind of thoughts are you interested ...

Check the dsenv script in your project directory and also the DataStage startup script in /bin for ulimit settings.

In the job properties you can specify a before-job subroutine and I believe one of the options is ExecSh or something similar to execute a UNIX shell command.

OK, put a "ulimit -a" external command into your job to make sure that the background process is getting the same limitations; perhaps one of your initialization scripts resets the limit.

wahil, good guess, and it might work most of the but it isn't correct. The DATA.30 and OVER.30 are components of a type 30 hashed file, and if entries are made to the table that cause an overflow the OVER.30 file will be modified as well so your method doesn't guarantee a good answer. Also, the prob...

You also need to remove the dataset as well and re-create it.

I think you need to stop and & restart the DataStage server after making the ulimit change, have you done that?

There are far too many variables to make any meaningful estimate. You could be doing great on space and one sngle SORT or AGGREGATION can blow estimates away. One of the basic laws of computing is that disk space will always be used to capacity when allocated But you could ensure that you use a spec...

What gets listed when you just type "at" without options? How does your job look in the schedule?

I just wrote a 60-second PX job. Starts with a row generator that generates 100 rows with just one column called "Test" of type VarChar(32). The "edit row" sets the values to cycle between "00001" and "00000002". The transform does a simple "TRIM(DSLink2.Test,'0','L')" and the output goes to a PEEK ...

Benouche - that is why I asked if something had broken. If the answer is that it is OK in development and showing an error in production then what you've described is the actual cause, if it is in the development environment or somewhere where it "used to" work then they have a problem.

They are separated by a space in your output. Change your query order to "SELECT CATEGORY, JOB FROM DS_JOBS WHERE CATEGORY LIKE ='AAB%" and you'll see the difference.

Your configuration contains a bad path.

...The current PATH is: {text removed}/local/app/oracle/product/9.2.0.6/bin:/binAPT_SAS_Driver in SAS_13

The last part of the string is a malformed expression, ":/binAPT_SAS_Driver" looks like you forgot a "/".

How do you differentiate a first and a second run in your sequence? It seems that the first run you start the job #2 and don't wait for it to complete, so when you call it a second time it is still running and causes the error you posted.

I am not clear on exactlywhat you are intending to do; but the error messages means that when you are trying to reset iyour job it is most likely still running.