Not sure I know what you mean - especially by the word "sample". If you are using QTEMP in your Java application, you need to be very careful. The iSeries can use multi-threaded jobs to service ODBC and JDBC database requests. This means that multiple user sessions in the client/server or web application are performing database I/O possibly through the same OS/400 job. Each session or "thread" uses its own memory variables and pointers but shares QTEMP at a job level. If your application sometimes seems to step on itself - this might be your issue. A user might log in and click a button and on occasion sees the wrong data - possibly from a different users request. Their QTEMP files are being shared. Use a permanent file, in a permanent library with some unique key field for each session. This will help in many other ways. SQL performance can be dramatically better without constantly re-creating temporary indexes. Also, the operating system access planning process will have a much easier time on your permanent database files.