Sorry, I didn't see the original post and it's somewhat outside my area of
expertise but it might be worth investigating SQL Server mode (I don't mean
the MS product, either).
There's a way of creating a connection in server mode rather than as a
client type job (if I read the document correctly) but as I have never been
able to find a use for it I know barely anything about it other than it
exists.
A link to an IBM document referring to what I am talking about as a starting
point is here:
http://www.redbooks.ibm.com/abstracts/tips0658.html?Open
regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic
Sent: Tuesday, 25 November 2008 7:37 p.m.
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL
Does that use a separate SQL connection from the CLI?
Not sure if this answers your question but... SQL on System i allows for
only one database connection at a time. *LOCAL database is 'this' LPAR.
'Other' databases are remaining iASPs, LPARs and other machines (could be on
i or not).
Does it potentially fight with other programs in the same job using the
CLI?
No, it's not a fighter, it's a lover :)
Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com
-----Original Message-----
Subject: SQL
Currently, when our CRM application uses SQL, it uses it through the
CLI, and since the CLI is evidently only allowed to have one active
connection per job, and we have two programs (so far) using SQL, both of
which would slow to a crawl if they had to create and destroy
connections every time, the SQL access goes through a proxy program that
makes the CLI API calls, and stores the connection.
Nobody here has ever used SQL RPG. Does that use a separate SQL
connection from the CLI? Does it potentially fight with other programs
in the same job using the CLI?
As an Amazon Associate we earn from qualifying purchases.