× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: AS/400 Toolkit - Closing Files
  • From: Don Strickland <dstrickland@xxxxxxx>
  • Date: Tue, 2 May 2000 16:46:43 -0700


Timothy,

I had the same difficulty when connecting my AS400 to an S390.  It's not
Java, it's the thread your using to communicate.   Try dynamically
allocating a non-main thread in Java, using that thread for your JDBC
application, then ending that thread without ending the main thread. It
worked on the S390.  I haven't encountered it here (new job).

Don Strickland
800.COM



-----Original Message-----
From: Timothy Sullivan [mailto:TSullivan@computer-guidance.com]
Sent: Tuesday, May 02, 2000 3:59 PM
To: JAVA400-L@midrange.com
Subject: AS/400 Toolkit - Closing Files


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
+---
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.