We've been experimenting with JSPBatchCompiler to pre-compile the JSPs in our WebFacing project. At one customer, the job runs for a while and then ends in error. Checking the QPRINT file I see the following: Translating /webfacing/jsp/DDSrecords/BSYSRC1/BSYSRCA/BSY855FM/h 8 JSPs were successfully translated. 0 JSPs had translation errors. 0 JSPs were up to date. Exception caught during processing java.io.IOException: Resource busy. /tmp/jsp2407files at java.lang.Throwable.<init>(Throwable.java:195) followed by the rest of the stack trace. I doubt that some job just happens to create a file with the same name, so what's going on? Is it possible that the entire /tmp directory is being locked? Rob