DB2 Connect V7 connection help with inactive threads

A. J. Zobjeck

DB2 Connect V7 connection help with inactive threads
We are using DB2 Connect for the first time with two applications and I'm
having an authorization problem.

First,

Application A comes in with Authorization id Y
Application B comes in with Authorization id Z

Once the applications returns an answer they go inactive (this is good).

But, if Application B then starts again it trys to use the thread with
authorization id Y and fails with a authorization error. Why would
application B use that inactive thread? I have to cancel the inactive DDF
threads to get it to work. Does any have an idea what is causing the
problem.

Also, application B is a stored procedure. I don't have any problems with
Application A.

Thanks.



Myron Miller

Re: DB2 Connect V7 connection help with inactive threads
(in response to A. J. Zobjeck)
When application A or Application B get an answer, do they close the result
set and close the connection or do they leave the connection open?

Normally, if the connection is actually closed, then the application must
connect again with a userid and password that is verified by the security
manager at your db2 site. If you're using some type of connection pooling
at your DB2 connect user machine, then its entirely possible that this is
causing your security problems.

-----Original Message-----
From: Zobjeck, A. J. [mailto:[login to unmask email]
Sent: Friday, November 16, 2001 8:45 AM
To: [login to unmask email]
Subject: DB2 Connect V7 connection help with inactive threads


We are using DB2 Connect for the first time with two applications and I'm
having an authorization problem.

First,

Application A comes in with Authorization id Y
Application B comes in with Authorization id Z

Once the applications returns an answer they go inactive (this is good).

But, if Application B then starts again it trys to use the thread with
authorization id Y and fails with a authorization error. Why would
application B use that inactive thread? I have to cancel the inactive DDF
threads to get it to work. Does any have an idea what is causing the
problem.

Also, application B is a stored procedure. I don't have any problems with
Application A.

Thanks.








A. J. Zobjeck

Re: DB2 Connect V7 connection help with inactive threads
(in response to Myron Miller)
Pooling is not being used.

-----Original Message-----
From: Myron Miller [mailto:[login to unmask email]
Sent: Friday, November 16, 2001 8:59 AM
To: [login to unmask email]
Subject: Re: DB2 Connect V7 connection help with inactive threads


When application A or Application B get an answer, do they close the result
set and close the connection or do they leave the connection open?

Normally, if the connection is actually closed, then the application must
connect again with a userid and password that is verified by the security
manager at your db2 site. If you're using some type of connection pooling
at your DB2 connect user machine, then its entirely possible that this is
causing your security problems.

-----Original Message-----
From: Zobjeck, A. J. [mailto:[login to unmask email]
Sent: Friday, November 16, 2001 8:45 AM
To: [login to unmask email]
Subject: DB2 Connect V7 connection help with inactive threads


We are using DB2 Connect for the first time with two applications and I'm
having an authorization problem.

First,

Application A comes in with Authorization id Y
Application B comes in with Authorization id Z

Once the applications returns an answer they go inactive (this is good).

But, if Application B then starts again it trys to use the thread with
authorization id Y and fails with a authorization error. Why would
application B use that inactive thread? I have to cancel the inactive DDF
threads to get it to work. Does any have an idea what is causing the
problem.

Also, application B is a stored procedure. I don't have any problems with
Application A.

Thanks.













Kurt Sahlberg

Re: DB2 Connect V7 connection help with inactive threads
(in response to A. J. Zobjeck)
Hi Al,
If you are using the access control authorization exit ([login to unmask email])
look at PQ43169 this is a match to your problem discription.
HTH
Kurt


>>> [login to unmask email] 11/16/01 07:45AM >>>
We are using DB2 Connect for the first time with two applications and I'm
having an authorization problem.

First,

Application A comes in with Authorization id Y
Application B comes in with Authorization id Z

Once the applications returns an answer they go inactive (this is good).

But, if Application B then starts again it trys to use the thread with
authorization id Y and fails with a authorization error. Why would
application B use that inactive thread? I have to cancel the inactive DDF
threads to get it to work. Does any have an idea what is causing the
problem.

Also, application B is a stored procedure. I don't have any problems with
Application A.

Thanks.






Ted Pesta

V7
(in response to Kurt Sahlberg)
We are looking at migrating from V5 to V7 instead of V6. I know V7 has been
GA since March 2001, but I've not heard that it's stable. I found the
archive articles by Roger Miller ( 13 Mar 2001) and Eric Pearson (12 Jun
2001). I was looking for more recent experiences.

Has anyone else migrated from V5 to V7, and is there a stable maintenance
level for V7?

Thanks,
Ted Pesta
AmQUEST, Inc.



John Vernon

Re: V7
(in response to Ted Pesta)
Roger Miller's Developer's Corner in IDUG SOLUTION JOURNAL VOL 8 NO 3 (I
just received my copy today) states that "V7 is looking very solid now"....

hth,
john

-----Original Message-----
From: Ted Pesta [mailto:[login to unmask email]
Sent: Monday, November 19, 2001 12:52 PM
To: [login to unmask email]
Subject: V7


We are looking at migrating from V5 to V7 instead of V6. I know V7 has been
GA since March 2001, but I've not heard that it's stable. I found the
archive articles by Roger Miller ( 13 Mar 2001) and Eric Pearson (12 Jun
2001). I was looking for more recent experiences.

Has anyone else migrated from V5 to V7, and is there a stable maintenance
level for V7?

Thanks,
Ted Pesta
AmQUEST, Inc.








Roger Miller

Re: V7
(in response to John Vernon)
I'm pretty cautious, since I get the complaints directly and often several
times. V7 looks very good. The V7 APAR backlog is about 20% of the V6
backlog. I try to chase down problem rumors, and the latest was not related
to the code, for example. For a service level recommendation, use the IBM
Consolidated Service Test.

http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/

Roger Miller, DB2 for z/OS



Ted Pesta

Re: V7
(in response to Roger Miller)
Thank you to everyone who responded. The help was very much appreciated.

Ted Pesta
AmQUEST, Inc.



-----Original Message-----
From: Roger Miller [mailto:[login to unmask email]
Sent: Tuesday, November 20, 2001 11:57 AM
To: [login to unmask email]
Subject: Re: V7

I'm pretty cautious, since I get the complaints directly and
often several
times. V7 looks very good. The V7 APAR backlog is about
20% of the V6
backlog. I try to chase down problem rumors, and the latest
was not related
to the code, for example. For a service level
recommendation, use the IBM
Consolidated Service Test.

http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/

Roger Miller, DB2 for z/OS


To change your subscription options or to cancel your
subscription visit the DB2-L webpage at http://www.ryci.com/db2-l. The
owners of the list can



A. J. Zobjeck

DB2 Connect V7 connection help with inactive threads
(in response to Ted Pesta)
We are using DB2 Connect v7 and DB2 v5 OS/390 for the first time with two
applications and I'm
having an authorization problem.

First,

Application A comes in with Authorization id Y
Application B comes in with Authorization id Z

Once the applications returns an answer their thread goes inactive (this is
good).

But, if Application B then starts again it trys to use the thread with
authorization id Y and fails with a authorization error. Why doesn't
application B use that inactive thread? I have to cancel the inactive DDF
threads to get it to work. Does anyone have an idea what is causing the
problem. Also, I've tried turned thread pooling on and off but, that
doesn't do anything.

One more comment, application B is a stored procedure. I don't have any
problems with
Application A.

Besides sys.procedures do I have enter some other information into a DB2
table?

Thanks.



teldb2kals

Re: DB2 Connect V7 connection help with inactive threads
(in response to A. J. Zobjeck)
We had this problem sometime back when we moved to DB2 Connect v5.2. We
then determined that the problem was being caused by the way our 16-bit
windows application was using the 32-bit ODBC driver. (the earlier
driver was 16-bit ODBC). Finally we wrote some sort of a wrapper (to
keep track of the connections) around the 32-bit ODBC API calls which
restored the correct connection context.

I am not able to recollect the exact details just now, but this might
give u some hints.

Cheers,
Kals

-----Original Message-----
From: Zobjeck, A. J. [SMTP:[login to unmask email]
Sent: Saturday, December 15, 2001 1:07 AM
To: [login to unmask email]
Subject: DB2 Connect V7 connection help with inactive threads

We are using DB2 Connect v7 and DB2 v5 OS/390 for the first time with
two
applications and I'm
having an authorization problem.

First,

Application A comes in with Authorization id Y
Application B comes in with Authorization id Z

Once the applications returns an answer their thread goes inactive
(this is good).

But, if Application B then starts again it trys to use the thread with
authorization id Y and fails with a authorization error. Why doesn't
application B use that inactive thread? I have to cancel the inactive
DDF threads to get it to work. Does anyone have an idea what is
causing the problem. Also, I've tried turned thread pooling on and off
but, that doesn't do anything.

One more comment, application B is a stored procedure. I don't have any
problems with Application A.

Besides sys.procedures do I have enter some other information into a DB2
table?

Thanks.



----------------
Powered by telstra.com