Binding CLI Packages for Distributed Applications Using Dynamic SQL

Kurt Sahlberg

Binding CLI Packages for Distributed Applications Using Dynamic SQL
Your assumption is correct.
You must explicitly grant privileges to users running the CLI packages.
Before DB2 UDB V6 OS390 and 3 part names we used CLI packages
to access remote NT databases.
We only use DYNAMICRULES(BIND) for static bound packages
that have dynamic SQL embedded within them on OS390.
Kurt

>>> [login to unmask email] 12/19/00 01:09PM >>>
Trying to confirm whether an assumption I'm under is correct. We're using
DB2 Connect to connect to the mainframe. It's my understanding that when
binding the CLI packages in DB2/OS390, you cannot specify
"DYNAMICRULES(BIND)" as a bind option, because (according to the Command
Reference Manual) this option cannot be used for binding packages that would
include SQL statements that cannot be dynamically prepared. This would
include, amoung other things, "SET CURRENT PACKAGESET" and "CONNECT".
Unless I'm missing something, any web or client server application program
accessing DB2/OS390 is going to execute the CONNECT statement, thereby
eliminating the option of binding the CLI packages with DYNAMICRULES(BIND).






Gerry McHugh

Re: Binding CLI Packages for Distributed Applications Using Dynam ic SQL
(in response to Kurt Sahlberg)
Kurt,

Thanks.

-----Original Message-----
From: Kurt Sahlberg [mailto:[login to unmask email]
Sent: Wednesday, December 20, 2000 12:00 PM
To: [login to unmask email]
Subject: Re: Binding CLI Packages for Distributed Applications Using
Dynamic SQL


Your assumption is correct.
You must explicitly grant privileges to users running the CLI packages.
Before DB2 UDB V6 OS390 and 3 part names we used CLI packages
to access remote NT databases.
We only use DYNAMICRULES(BIND) for static bound packages
that have dynamic SQL embedded within them on OS390.
Kurt

>>> [login to unmask email] 12/19/00 01:09PM >>>
Trying to confirm whether an assumption I'm under is correct. We're using
DB2 Connect to connect to the mainframe. It's my understanding that when
binding the CLI packages in DB2/OS390, you cannot specify
"DYNAMICRULES(BIND)" as a bind option, because (according to the Command
Reference Manual) this option cannot be used for binding packages that would
include SQL statements that cannot be dynamically prepared. This would
include, amoung other things, "SET CURRENT PACKAGESET" and "CONNECT".
Unless I'm missing something, any web or client server application program
accessing DB2/OS390 is going to execute the CONNECT statement, thereby
eliminating the option of binding the CLI packages with DYNAMICRULES(BIND).








http://www.ryci.com/db2-l. The owners of the list can be reached at
[login to unmask email]