DSXchange

What File(s) in which location(s) is/are being created and not deleted that cause the file system(s) to run full?

Could you put a transform stage between your "real" transform and the output sequential file. How many rows does the log show went through that transform stage with a setting of "0" and "1"?

Could you put a transform stage between your "real" transform and the output sequential file. How many rows does the log show went through that transform stage with a setting of "0" and "1"?

Try opening a DOS window and using the "cd {yourpath}" command - does that work? Are you using variables or parameters for your paths or are they hardcoded? Have you tried using view data in the designer?

Try opening a DOS window and using the "cd {yourpath}" command - does that work? Are you using variables or parameters for your paths or are they hardcoded? Have you tried using view data in the designer?

The Transformer stage cannot be used for your intended purpose, because there is no way to detect that the last row is being read. As mentioned before, an Aggregator stage will do that.

Are you certain that the hashed file exists in the new Project? What parameters are you passing to the routine?

Are you certain that the hashed file exists in the new Project? What parameters are you passing to the routine?

Did you install the same optional components on both systems? It looks like defaulted empty values are being added to one and not the other export files and it shouldn't make a difference in execution.

The only problem could be indices, if you have them on the files.

The CATALOG command puts routines in the system catalog, not hashed files. Or do you mean that you are using the FILE.CACHE commands?

The heap is a temporary space allocation, so the disk will quickly run full then empty again and you might have missed it.

Have you tried doing a Save-As another name? If that works, delete the original job and then rename your copy. At V8 it is a bit more difficult to recover from this type of problem than at previous versions, as you also have the repository to deal with and the error could be in either place. Do you ...

Yes, I've been successful using DataDirect drivers to a V7 DataStage on Solaris.

Don't you still need the "-mode NORMAL"?

Ernie - I know that there is, but I seem to recall it is different on different versions on Linux as well. Scope/krishna - The fork failed error is certainly caused by a setting of maxuproc too low, but a value of only 100 is far too little for PX to work; even a medium sized job with several nodes ...