Re: ODBC vs SQL CLI Connection Speed

Elvis,

Thanks for the tip, and it should be useful in a production setting, but I'm 
the only user on my development box at the moment, and there are currently five 
(5) QSQSRVR prestart jobs active, with only one (1) in use.

iSeries Access offers ODBC connection pooling:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzaik/connectionpooling.htm

Maybe it would help if IBM offered something similar for SQL CLI connections.  
Or maybe some other environmental setting would help?

Nathan.



----- Original Message ----
From: Elvis Budimlic <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, August 31, 2006 11:02:51 AM
Subject: RE: ODBC vs SQL CLI Connection Speed

CLI jobs are served by QSQSRVR jobs. Perhaps you don't prestart enough of
them.  Checkout DSPACTPJ and CHGPJE commands for more details.

Elvis

-----Original Message-----
Subject: ODBC vs SQL CLI Connection Speed

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.