Re: SQL CLI and connecting to RDBs

["Carel Teijgeler" <coteijgeler@xxxxxxxxx>]

Tom,

I think the wording of the document are not that precise. The wording of reason 
1 and 3 are a little strange. But I can guess.

Reason 2 is obvious: you only have to connect to a RDB once to run multple SQL 
statements onthat RDB. You can connect to one or more different RDBs. 
I think the CLI Server Mode is a multi threaded job, which allow one job, one 
programme connect multiple times to the same RDB.

Multi threading would also explain reason 1: each thread runs in its own 
activation group.

Reason 3 seems to me that you only have to connect with one registered user 
profile and password to other RDBs, while serving multiple requests from local 
users.

Just my interpretation, though.

Regards,
Carel Teijgeler

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

On 16-11-05 at 19:25 qsrvbas@xxxxxxxxxxxx wrote:

>I ran across this today...
>
>" What is CLI Server Mode?
>
>Server mode was introduced in V4R2 in a functional PTF. The reason for
>running in SQL server mode is that many applications have the need to act
>as database servers. This means that a single job will execute SQL
>requests on behalf of multiple users. In our current SQL implementation, this 
>does not work for 3 reasons:
>
>1) A single job can only have one commit transaction per activation group
>2) A single job can only connect to an RDB once
>3) All SQL statements run under the job's user profile, regardless of the 
>userid passed in on the connect
>
>SQL server mode will solve these 3 problems by routing all SQL statements to a 
>separate job. ..."
>
>The document is:
>
>http://www-03.ibm.com/servers/eserver/iseries/db2/clifaq.htm#header_3
>
>The pieces that interest me are:
>  2) A single job can only connect to an RDB once
>...along with:
>  "SQL server mode will solve these 3 problems..."
>
>Does anybody have a useful explanation of what those two items mean together?