DB2 Connect & Set Current SQLID

Steve Whittaker

DB2 Connect & Set Current SQLID
Wonder if anyone can give me some help on this.
We currently are running DB2 Connect v7.2 EE and also Run Time Client v7.2
with Fixpack 5 installed.

Question:
I have a logon-id that is named QCMUSER and when it comes thru DB2 Connect
and trys to select from a
particular table it fails with QCMUSER.TABLEA not defined. Which is a true
stmt. Its tacking on the QCMUSER
id as the table owner and that is not correct. I know that in the DB2 V6
OS/390 world I can create an ALIAS for
QCMUSER that will take care of this problem. (I think)
What I've seen is on DB2 Connect the Client Configuration Assistant, under
SETTINGS there is a section
called ENTERPRISE that has a reference to CURRENT SQLID. From what I can
read I should be able to
put in the HLQ of the table in here and when QCMUSER logs on I would think
that it would know that the current sqlid
should be EEPP in this case. But it doesn't seem to work, it still trys to
tack on the QCMUSER id as the owner.
Has anyone played around with this or can give me a hint at what I might be
doing wrong? The objective is for
our clients not to have to qualify the tables between test and prod, if
thats possible. I was wondering if this can
be controlled at the Run Time Client desktop or at the Enterprise server.
Appreciate any comments/suggestions.

Thank-you:
--Steve....



Dave Shapiro

Re: DB2 Connect & Set Current SQLID
(in response to Steve Whittaker)
Steve,

I've tried to use it in the past and could not get it to work either. Just tried it again and same results as you. FYI, also in the Enterprise tab is a supposed filter for DBNAME, but have never been able to get it to work either. I'm tempted to ask IBM, but if you do before me, or if anyone else knows, please share your findings.

Thanks

Dave

-----Original Message-----
From: Whittaker, Stephen [mailto:[login to unmask email]
Sent: Thursday, January 09, 2003 12:17 PM
To: [login to unmask email]
Subject: DB2 Connect & Set Current SQLID



Wonder if anyone can give me some help on this.
We currently are running DB2 Connect v7.2 EE and also Run Time Client v7.2 with Fixpack 5 installed.

Question:
I have a logon-id that is named QCMUSER and when it comes thru DB2 Connect and trys to select from a
particular table it fails with QCMUSER.TABLEA not defined. Which is a true stmt. Its tacking on the QCMUSER
id as the table owner and that is not correct. I know that in the DB2 V6 OS/390 world I can create an ALIAS for
QCMUSER that will take care of this problem. (I think)
What I've seen is on DB2 Connect the Client Configuration Assistant, under SETTINGS there is a section
called ENTERPRISE that has a reference to CURRENT SQLID. From what I can read I should be able to
put in the HLQ of the table in here and when QCMUSER logs on I would think that it would know that the current sqlid
should be EEPP in this case. But it doesn't seem to work, it still trys to tack on the QCMUSER id as the owner.
Has anyone played around with this or can give me a hint at what I might be doing wrong? The objective is for
our clients not to have to qualify the tables between test and prod, if thats possible. I was wondering if this can
be controlled at the Run Time Client desktop or at the Enterprise server.
Appreciate any comments/suggestions.

Thank-you:
--Steve....



Craig Theisen

Re: DB2 Connect & Set Current SQLID
(in response to Dave Shapiro)
We have also hit something similar and as I recall what we did to solve
it go into the Enterprise tab and entering your EEPP in the schema list and
current SQLID, and also check the current SQLID box on the schema list
tab.

Craig Theisen
Database Administration
GuideOne Insurance

-----Original Message-----
From: Shapiro, Dave [mailto:[login to unmask email]
Sent: Thursday, January 09, 2003 2:46 PM
To: [login to unmask email]
Subject: Re: DB2 Connect & Set Current SQLID


Steve,

I've tried to use it in the past and could not get it to work either. Just
tried it again and same results as you. FYI, also in the Enterprise tab is
a supposed filter for DBNAME, but have never been able to get it to work
either. I'm tempted to ask IBM, but if you do before me, or if anyone else
knows, please share your findings.

Thanks

Dave

-----Original Message-----
From: Whittaker, Stephen [mailto:[login to unmask email]
Sent: Thursday, January 09, 2003 12:17 PM
To: [login to unmask email]
Subject: DB2 Connect & Set Current SQLID



Wonder if anyone can give me some help on this.
We currently are running DB2 Connect v7.2 EE and also Run Time Client v7.2
with Fixpack 5 installed.

Question:
I have a logon-id that is named QCMUSER and when it comes thru DB2 Connect
and trys to select from a
particular table it fails with QCMUSER.TABLEA not defined. Which is a true
stmt. Its tacking on the QCMUSER
id as the table owner and that is not correct. I know that in the DB2 V6
OS/390 world I can create an ALIAS for
QCMUSER that will take care of this problem. (I think)
What I've seen is on DB2 Connect the Client Configuration Assistant, under
SETTINGS there is a section
called ENTERPRISE that has a reference to CURRENT SQLID. From what I can
read I should be able to
put in the HLQ of the table in here and when QCMUSER logs on I would think
that it would know that the current sqlid
should be EEPP in this case. But it doesn't seem to work, it still trys to
tack on the QCMUSER id as the owner.
Has anyone played around with this or can give me a hint at what I might be
doing wrong? The objective is for
our clients not to have to qualify the tables between test and prod, if
thats possible. I was wondering if this can
be controlled at the Run Time Client desktop or at the Enterprise server.
Appreciate any comments/suggestions.

Thank-you:
--Steve....



[login to unmask email]

Re: DB2 Connect & Set Current SQLID
(in response to Craig Theisen)
Steve, Dave,

Maybe you're not connecting through CLI/ODBC so the setting is not being
picked up. One way to test this is to run your command using db2batch
using the -cli option. Using that option it should pick up your SQLID
setting, and without that option it won't.

Steve Toeniskoetter
American Electric Power








"Shapiro, Dave"
<[login to unmask email] To: [login to unmask email]
CIPAL.COM> cc:
Sent by: DB2 Data Subject: Re: [DB2-L] DB2 Connect & Set Current SQLID
Base Discussion
List
<[login to unmask email]
ASSOC.COM>


01/09/03 03:45 PM
Please respond to
DB2 Data Base
Discussion List






Steve,

I've tried to use it in the past and could not get it to work either. Just
tried it again and same results as you. FYI, also in the Enterprise tab is
a supposed filter for DBNAME, but have never been able to get it to work
either. I'm tempted to ask IBM, but if you do before me, or if anyone
else knows, please share your findings.

Thanks


Dave


-----Original Message-----
From: Whittaker, Stephen [mailto:[login to unmask email]
Sent: Thursday, January 09, 2003 12:17 PM
To: [login to unmask email]
Subject: DB2 Connect & Set Current SQLID



Wonder if anyone can give me some help on this.
We currently are running DB2 Connect v7.2 EE and also Run Time Client
v7.2 with Fixpack 5 installed.


Question:
I have a logon-id that is named QCMUSER and when it comes thru DB2
Connect and trys to select from a
particular table it fails with QCMUSER.TABLEA not defined. Which is a
true stmt. Its tacking on the QCMUSER
id as the table owner and that is not correct. I know that in the DB2
V6 OS/390 world I can create an ALIAS for
QCMUSER that will take care of this problem. (I think)
What I've seen is on DB2 Connect the Client Configuration Assistant,
under SETTINGS there is a section
called ENTERPRISE that has a reference to CURRENT SQLID. From what I
can read I should be able to
put in the HLQ of the table in here and when QCMUSER logs on I would
think that it would know that the current sqlid
should be EEPP in this case. But it doesn't seem to work, it still
trys to tack on the QCMUSER id as the owner.
Has anyone played around with this or can give me a hint at what I
might be doing wrong? The objective is for
our clients not to have to qualify the tables between test and prod,
if thats possible. I was wondering if this can
be controlled at the Run Time Client desktop or at the Enterprise
server.
Appreciate any comments/suggestions.


Thank-you:
--Steve....



Dave Shapiro

Re: DB2 Connect & Set Current SQLID
(in response to sjtoeniskoetter@AEP.COM)
Hello Craig,

Say hello to Glenn for me as well!

I still get my login userid as the HLQ, and I have schemalist set, and current SQLID checked (which adds to the schemalist parm and makes me think that I am asking for whatever is the current sqlid to be part of the table filter?). Please let me know if you think of what else I may be missing.

Anyone ever get DBNAME to work as a filter?

Thanks!

Dave

-----Original Message-----
From: Theisen, Craig [mailto:[login to unmask email]
Sent: Thursday, January 09, 2003 3:20 PM
To: [login to unmask email]
Subject: Re: DB2 Connect & Set Current SQLID


We have also hit something similar and as I recall what we did to solve
it go into the Enterprise tab and entering your EEPP in the schema list and
current SQLID, and also check the current SQLID box on the schema list
tab.

Craig Theisen
Database Administration
GuideOne Insurance

-----Original Message-----
From: Shapiro, Dave [mailto:[login to unmask email]
Sent: Thursday, January 09, 2003 2:46 PM
To: [login to unmask email]
Subject: Re: DB2 Connect & Set Current SQLID


Steve,

I've tried to use it in the past and could not get it to work either. Just
tried it again and same results as you. FYI, also in the Enterprise tab is
a supposed filter for DBNAME, but have never been able to get it to work
either. I'm tempted to ask IBM, but if you do before me, or if anyone else
knows, please share your findings.

Thanks

Dave

-----Original Message-----
From: Whittaker, Stephen [mailto:[login to unmask email]
Sent: Thursday, January 09, 2003 12:17 PM
To: [login to unmask email]
Subject: DB2 Connect & Set Current SQLID



Wonder if anyone can give me some help on this.
We currently are running DB2 Connect v7.2 EE and also Run Time Client v7.2
with Fixpack 5 installed.

Question:
I have a logon-id that is named QCMUSER and when it comes thru DB2 Connect
and trys to select from a
particular table it fails with QCMUSER.TABLEA not defined. Which is a true
stmt. Its tacking on the QCMUSER
id as the table owner and that is not correct. I know that in the DB2 V6
OS/390 world I can create an ALIAS for
QCMUSER that will take care of this problem. (I think)
What I've seen is on DB2 Connect the Client Configuration Assistant, under
SETTINGS there is a section
called ENTERPRISE that has a reference to CURRENT SQLID. From what I can
read I should be able to
put in the HLQ of the table in here and when QCMUSER logs on I would think
that it would know that the current sqlid
should be EEPP in this case. But it doesn't seem to work, it still trys to
tack on the QCMUSER id as the owner.
Has anyone played around with this or can give me a hint at what I might be
doing wrong? The objective is for
our clients not to have to qualify the tables between test and prod, if
thats possible. I was wondering if this can
be controlled at the Run Time Client desktop or at the Enterprise server.
Appreciate any comments/suggestions.

Thank-you:
--Steve....






Juan Calleja Vilar

Re: DB2 Connect & Set Current SQLID
(in response to Dave Shapiro)
Hello Stephen, Dave and Craig.

We have set the CURRENTSQLID parameter and have noticed that it only
works fine when accessing through an application running under DB2 Connect.
But if we use the interactive query tools provided by DB2 Connect (Command
line processor, Command Center, ...) it is neccessary to execute an explicit
SET CURRENT SQLID statement.

Hope this helps.

Juan Calleja Vilar
IBERDROLA, S.A.