|
Dean Clowe wrote: >I find that JDBC access is very slow when connecting >to a remote database on the AS/400. [much more deleted] The way you describe the problem suggests to me that the issue is strictly comm bandwidth (the 56Kbits per second line). Accordingly, you might look into ways using ordinary Sockets, RMI, or maybe data queues (using Toolbox) to do more of the work on the server side, minimizing the amount of data sent over the wire. Given that you are in Java, this might not be so painful as you might initially think, even if you end up moving several of your jar files en masse to the AS/400. I've worked with several customers and the portability story is often very good indeed. Ordinary JDBC via toolbox drags the data to the remote computer; you should look for an approach which sends the data to the AS/400 computer and does the JDBC access there. At the end of the day, you still have to send data over the wire, so even this may not be enough to satisfy you; 56kbits is fundamentally limited after all. But, you should at least explore if you can keep the actual data flow between the client and the host minimal via the suggestions I just made. If you can send the data and some simple byte sequences giving instructions, having functions like read-for-update followed by update all happen on the host might be just the ticket for you. Larry W. Loen - Senior Java and AS/400 Performance Analyst Dept HP4, Rochester MN -- These are my opinions, not IBM's +--- | 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 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.