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



Tom,

As I have understood from the manuals, you only need one environment handle and 
at least one connection handle to connect to an RDB. for each RDB to connect to 
you have to create a connection handle. So you can have one to multiple 
statements handles associated to a connection handle.

>From the manuals:

"SQLAllocConnect API. 
SQLAllocConnect() allocates a connection handle and associated resources within 
the environment identified by the input environment handle. Call SQLGetInfo() 
with fInfoType set to SQL_ACTIVE_CONNECTIONS, to query the number of 
connections that can be allocated at any one time. 

SQLAllocEnv() must be called before calling this function."

I do not know if this is possible with an interactive single job SQL CLI 
programme, but it seems possible. I have not tested this.

Regards,
Carel Teijgeler 

*********** REPLY SEPARATOR  ***********

On 17-11-05 at 17:08 qsrvbas@xxxxxxxxxxxx wrote:

>I agree that the wording seems imprecise, but I don't think #2 is at all 
>obvious.
>
>If multiple users are submitting SQL statements, there's no reason to
>expect that they are _all always_ connected to the _same_ RDB. There seems
>to be an implication here that CLI Server mode opens a potential path for
>concurrent connections to multiple RDBs.
>
>How that might be put to advantage, I have no idea -- nor any idea even
>_if_ it can. It just seems to open a different window of opportunity.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.