Prev: db2 not started?
Next: Removing XML Extender
From: Ian on 29 Dec 2009 10:49
Hi,

I know that if I set a special register (such as CURRENT SCHEMA or
CURRENT REFRESH AGE) inside a stored procedure, the special registers
are set only in the scope of the stored procedure.

Is there a way that a stored procedure can set special registers for
the calling application? (i.e. I'm thinking of a stored procedure
that would initialize an application's environment).


Thanks,

From: Serge Rielau on 29 Dec 2009 11:43
On 12/29/2009 10:49 AM, Ian wrote:
> Hi,
>
> I know that if I set a special register (such as CURRENT SCHEMA or
> CURRENT REFRESH AGE) inside a stored procedure, the special registers
> are set only in the scope of the stored procedure.
>
> Is there a way that a stored procedure can set special registers for
> the calling application? (i.e. I'm thinking of a stored procedure
> that would initialize an application's environment).
Unfortunately not. You need to use the JDBc connectio string or CLI.ini
or whatever your client offers.
There is alos (I think) an option for central management via Optim.
that is the client will query the setup from a central location. that
has benefits if you want to roll out changes across multiple instances
and multiple clients.
I don't have a link handy.. i just heard about it myself.

--
Serge Rielau
SQL Architect DB2 for LUW
IBM Toronto Lab

 | 
Pages: 1
Prev: db2 not started?
Next: Removing XML Extender