AS/400 Toolkit - Closing Files

[Timothy Sullivan <TSullivan@xxxxxxxxxxxxxxxxxxxxx>]

Hello,

        We are currently developing an Java application using the AS/400
toolkits JDBC driver.  The application uses one connection to the AS/400
that is started when the user logs in and is not closed until the user exits
the application.  This connection is used to create all Statements object.
The problem is that in certain cases when we call Statement.close() the file
on the AS/400 is left open.  

        On the AS/400 I use the command  "wrksbsjob qserver" and find the
job QZDASOINI that corresponds to my session and check my open files.  The
files QQAZDTBL1, QQAZDTBL4, QQAZDTBL7, and QQAZDCOLM are always open and
remain so until we close the connection.  I assume that these are necessary
for the JDBC connection.  Next I open a few Statement objects in Java,
execute queries, and then call Statement.close() on each opened statement.
However, some of the files I just queried are not closed according to the
AS/400.  They seemed to have been left open even after executing a
Statement.close() in Java.    The open files are closed when the Connection
is closed, but closing the connection defeats our application persistence
design and is costly in terms of performance.  It would seem that after
closing the Java Statement object the corresponding file on the AS/400 that
was queried would also close.  Has anyone seen this behavior?  Any
suggestion on to what is going on?  Am I look at this the correct way? 

/Thanks
Timothy Sullivan
Senior Java Developer
 
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---