× 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.



When I use the SQL  CLI sqlConnect() function to establish a connection with a 
local database from  an RPG program there's quite a noticeable delay in setting 
up the connection,  but when I use the sqlConnect() function within an ODBC 
client to establish a  connection with an iSeries Access ODBC data source, the 
response is  instantaneous.
  
 In the case of the  ODBC client, the connection is established with one of the 
QZDASOINIT server  jobs.  In the case of the SQL CLI interface, the connection 
is established with  one of the QSQSRVR jobs.
  
 Why is the ODBC  connection so much faster?  One guess, is that the iSeries 
Access ODBC driver is  managing a pool of connections, while the SQL CLI 
interface is establishing a  new connection.  But that's just a guess.
  
 Is there a way to  increase the speed of establishing SQL CLI connections?
  
 Thanks,
  
 Nathan.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.