DSXchange

/dstage/tmp ran out of space. It might have been a one-off issue during the failed run, with other jobs using that same space.

So, you've broken that line into two and this is what is causing your problem. Go into VI and fix it by combining the lines with "J"

Is the LD_LIBRARY_PATH all on one line in the editor?

edit your dsenv file. find the line containing "jre/lib/i386:/" and past the previous 2 and subsequent 2 to this thread.

Your dsenv script is corrupted. It looks like someone hit a <cr> in the middle of the long line that sets your LIBPATH, and perhaps the PATH as well.

Sai, usually "dsenv" script in the $DSHOME directory will contain all the commands necessary to set up the environment, you should execute this to correctly put in your library search rules as well.

Can you make a copy of your job, and then remove everything from the BASIC transform stage and just copy the columns 1:1 from input to output and re-compile and re-run the job. If the error goes away you should look into your transform stage for functions that might not be present.

Then that means your source is probably a sequential file. You need to specify the non-default date format in your column options.

I would suggest that you check the log files to ensure that both the good and the bad run used the same APT_CONFIG file, I suspect that the didn't.

Aquilis - you have posted your generated code, but haven't told us what error you are getting at compilation.

I've tried unsuccessfully to install DS on LINUX versions apart from the support Red Hat AS version with no success.

This answer might also change if you are using a partitioned DB2 database as source/target/lookup as well.

Resinstalling to the directory should work. What happens - "no luck" isn't a great help in analyzing the problem.

Sure, 46570 is a process number so your search of DSJOBS won't return anything. I assume you missed the trailing "e" on Zombi. This would be a process that is waiting on a signal from a process that no longer exists.I'm not sure from the context if you even have a pid 46570 on your system and even l...

Hello and welcome to DSXChange.

This error is being raised from your after-job routine. You probably copied an existing job and then deleted the stages (I've done this many times before as well). Go to your job properties and remove the before-job and after-job routine calls.