DB2 UDB Control Center - SET CURRENT SQLID?

James D. Hannis

DB2 UDB Control Center - SET CURRENT SQLID?
In Control Center, I am able to execute a RUNSTATS utility against a DB2
OS/390 tablespace using my login user id even though that id does not
have explicit DB2 authority to do so - my guess is that this is because
SYUTILS has PUBLIC EXECUTE authority. However, when I try to GRANT
RUNSTATS authority to another user via the Control Center,
I get a -551. I can do this GRANT via SPUFI by first executing a SET
CURRENT SQLID to a different SQL authorization id that has SYSADM
authority. Is there a way to issue a SET CURRENT SQLID via Control
Center?


Jim Hannis
Database - WHQKO
(847) 700-4359
Pager (877) 861-7495

Claude Birtz

Re: DB2 UDB Control Center - SET CURRENT SQLID?
(in response to James D. Hannis)
Hello Jim,

you can do this through the client configuration assistant. When you highlight a connection, chose "Properties". you get prompted to connect to the data source. Then you have to chose CLI/ODBC parameters. You get a bigger window where you can set the SQLID under the tab "enterprise".

Our DB2/Connect and Control Center are in French, so I'm not sure if all the buttons / texts are the same. But I can send you the Word document with screen shots, explaining how to set the SQLID, I made for my colleagues. The document is in French too, but from the screen shots you should find your way.

Another, less "official" way would be to update the db2cli.ini file. After the entry of the location name, you can specify the SQLID with this entry: CURRENTSQLID=xxxxx.

I'm not sure if this is exactly what you want, as this SQLID will be
valid for the whole connection.

Hope this helps,

Claude.

On Thu, 26 Dec 2002 14:24:18 -0600
Jim Hannis <[login to unmask email]> wrote:

> In Control Center, I am able to execute a RUNSTATS utility against a DB2
> OS/390 tablespace using my login user id even though that id does not
> have explicit DB2 authority to do so - my guess is that this is because
> SYUTILS has PUBLIC EXECUTE authority. However, when I try to GRANT
> RUNSTATS authority to another user via the Control Center,
> I get a -551. I can do this GRANT via SPUFI by first executing a SET
> CURRENT SQLID to a different SQL authorization id that has SYSADM
> authority. Is there a way to issue a SET CURRENT SQLID via Control
> Center?
>
>
> Jim Hannis
> Database - WHQKO
> (847) 700-4359
> Pager (877) 861-7495
>

--
--------------------------------------------------------------------
Claude Birtz CIE
Tel: 49 925 622 Fax: 49 925 750
mailto:[login to unmask email]
--------------------------------------------------------------------



James D. Hannis

Re: DB2 UDB Control Center - SET CURRENT SQLID?
(in response to Claude Birtz)
Thanks, Claude. Your first recommendation worked just fine.

Regards,

Jim Hannis
Database - WHQKO
(847) 700-4359
Pager (877) 861-7495

-----Original Message-----
From: [login to unmask email] [SMTP:[login to unmask email]
Sent: Friday, December 27, 2002 3:29 AM
To: [login to unmask email]
Cc: [login to unmask email]
Subject: Re: DB2 UDB Control Center - SET CURRENT SQLID?

Hello Jim,

you can do this through the client configuration assistant. When you
highlight a connection, chose "Properties". you get prompted to
connect to the data source. Then you have to chose CLI/ODBC
parameters. You get a bigger window where you can set the SQLID under
the tab "enterprise".

Our DB2/Connect and Control Center are in French, so I'm not sure if
all the buttons / texts are the same. But I can send you the Word
document with screen shots, explaining how to set the SQLID, I made
for my colleagues. The document is in French too, but from the screen
shots you should find your way.

Another, less "official" way would be to update the db2cli.ini file.
After the entry of the location name, you can specify the SQLID with
this entry: CURRENTSQLID=xxxxx.

I'm not sure if this is exactly what you want, as this SQLID will be
valid for the whole connection.

Hope this helps,

Claude.

On Thu, 26 Dec 2002 14:24:18 -0600
Jim Hannis <[login to unmask email]> wrote:

> In Control Center, I am able to execute a RUNSTATS utility against
a DB2
> OS/390 tablespace using my login user id even though that id does
not
> have explicit DB2 authority to do so - my guess is that this is
because
> SYUTILS has PUBLIC EXECUTE authority. However, when I try to GRANT
> RUNSTATS authority to another user via the Control Center,
> I get a -551. I can do this GRANT via SPUFI by first executing a
SET
> CURRENT SQLID to a different SQL authorization id that has SYSADM
> authority. Is there a way to issue a SET CURRENT SQLID via Control
> Center?
>
>
> Jim Hannis
> Database - WHQKO
> (847) 700-4359
> Pager (877) 861-7495
>

--
--------------------------------------------------------------------
Claude Birtz CIE
Tel: 49 925 622 Fax: 49 925 750
mailto:[login to unmask email]
--------------------------------------------------------------------



visit the DB2-L webpage at http://listserv.ylassoc.com. The owners of
the list can