DRDA re-bind problem

Sibimon Philip

DRDA re-bind problem
We are testing DRDA from SQLserver using Grandview ODBC driver to DB2 V5.1
on OS/390 V2.6. After I execute the package from client/server, it looks
like the thread is still active. Display thread shows as follows

DSNV401I = DISPLAY THREAD REPORT FOLLOWS -
DSNV402I = ACTIVE THREADS -
NAME ST A REQ ID AUTHID PLAN ASID TOKEN
SERVER RA * 7 ws-dal-l3728 L3728 DISTSERV 004A 26342
V437-WORKSTATION=SYSB, USERID=l3728 ,
APPLICATION NAME=ws-dal-l3728_317_l3728
V445-SEANETA.JBDX.07CF0C0E2646=26342 ACCESSING DATA FOR <JBDX>:JBDX
V447--LOCATION SESSID A ST TIME
V448--<JBDX> F0000000000017EC W R2 9934814191741
DISPLAY ACTIVE REPORT COMPLETE
DSN9022I = DSNVDT '-DIS THREAD' NORMAL COMPLETION
***
Even though I got the result back, since this thread is active, I am not
able to re-bind this package in DB2I in mainframe.The re-bind is telling,
the resource is unavailable. My question is why this thread is active even
after the completion of the execution. I appreciate if anybody knows the
reason and solution for this.

thanks
Sibimon Philip
972-702-2515 - Office
972-417-3597 - Residence
E-mail - [login to unmask email]



craig patton

Re: DRDA re-bind problem
(in response to Sibimon Philip)
Philip,

What values in the BIND were specified for Connect/Disconnect? If defined
as EXPLICIT, and the application is NOT specifying DISCONNECT, I believe the
thread would stay active until a timeout threshold (if defined).

HTH
Craig Patton
DB2 DBA


>From: "Philip, Sibimon" <[login to unmask email]>
>Reply-To: DB2 Data Base Discussion List <[login to unmask email]>
>To: [login to unmask email]
>Subject: DRDA re-bind problem
>Date: Tue, 14 Dec 1999 14:34:57 -0500
>
>We are testing DRDA from SQLserver using Grandview ODBC driver to DB2 V5.1
>on OS/390 V2.6. After I execute the package from client/server, it looks
>like the thread is still active. Display thread shows as follows
>
>DSNV401I = DISPLAY THREAD REPORT FOLLOWS -
>DSNV402I = ACTIVE THREADS -
>NAME ST A REQ ID AUTHID PLAN ASID TOKEN
>SERVER RA * 7 ws-dal-l3728 L3728 DISTSERV 004A 26342
> V437-WORKSTATION=SYSB, USERID=l3728 ,
> APPLICATION NAME=ws-dal-l3728_317_l3728
> V445-SEANETA.JBDX.07CF0C0E2646=26342 ACCESSING DATA FOR <JBDX>:JBDX
> V447--LOCATION SESSID A ST TIME
> V448--<JBDX> F0000000000017EC W R2 9934814191741
>DISPLAY ACTIVE REPORT COMPLETE
>DSN9022I = DSNVDT '-DIS THREAD' NORMAL COMPLETION
>***
>Even though I got the result back, since this thread is active, I am not
>able to re-bind this package in DB2I in mainframe.The re-bind is telling,
>the resource is unavailable. My question is why this thread is active even
>after the completion of the execution. I appreciate if anybody knows the
>reason and solution for this.
>
>thanks
>Sibimon Philip
>972-702-2515 - Office
>972-417-3597 - Residence
>E-mail - [login to unmask email]
>
>
>
>
>

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com



Sibimon Philip

Re: DRDA re-bind problem
(in response to craig patton)
Craig,

The Disconnect is parameter for plan and the plan name for DRDA seems to be
DISTSERV. I am not able to find this plan in Sysibm.sysplan.

Sibimon Philip
972-702-2515 - Office
972-417-3597 - Residence
E-mail - [login to unmask email]


-----Original Message-----
From: craig patton [mailto:[login to unmask email]
Sent: Tuesday, December 14, 1999 1:56 PM
To: [login to unmask email]
Subject: Re: DRDA re-bind problem


Philip,

What values in the BIND were specified for Connect/Disconnect? If defined
as EXPLICIT, and the application is NOT specifying DISCONNECT, I believe the
thread would stay active until a timeout threshold (if defined).

HTH
Craig Patton
DB2 DBA


>From: "Philip, Sibimon" <[login to unmask email]>
>Reply-To: DB2 Data Base Discussion List <[login to unmask email]>
>To: [login to unmask email]
>Subject: DRDA re-bind problem
>Date: Tue, 14 Dec 1999 14:34:57 -0500
>
>We are testing DRDA from SQLserver using Grandview ODBC driver to DB2 V5.1
>on OS/390 V2.6. After I execute the package from client/server, it looks
>like the thread is still active. Display thread shows as follows
>
>DSNV401I = DISPLAY THREAD REPORT FOLLOWS -
>DSNV402I = ACTIVE THREADS -
>NAME ST A REQ ID AUTHID PLAN ASID TOKEN
>SERVER RA * 7 ws-dal-l3728 L3728 DISTSERV 004A 26342
> V437-WORKSTATION=SYSB, USERID=l3728 ,
> APPLICATION NAME=ws-dal-l3728_317_l3728
> V445-SEANETA.JBDX.07CF0C0E2646=26342 ACCESSING DATA FOR <JBDX>:JBDX
> V447--LOCATION SESSID A ST TIME
> V448--<JBDX> F0000000000017EC W R2 9934814191741
>DISPLAY ACTIVE REPORT COMPLETE
>DSN9022I = DSNVDT '-DIS THREAD' NORMAL COMPLETION
>***
>Even though I got the result back, since this thread is active, I am not
>able to re-bind this package in DB2I in mainframe.The re-bind is telling,
>the resource is unavailable. My question is why this thread is active even
>after the completion of the execution. I appreciate if anybody knows the
>reason and solution for this.
>
>thanks
>Sibimon Philip
>972-702-2515 - Office
>972-417-3597 - Residence
>E-mail - [login to unmask email]
>
>
>
>
>

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com








Kurt Sahlberg

Re: DRDA re-bind problem
(in response to Sibimon Philip)
DRDA uses packages not plans check sysibm.syspackage.
Kurt


>>> "Philip, Sibimon" <[login to unmask email]> 12/15/99 12:12PM >>>
Craig,

The Disconnect is parameter for plan and the plan name for DRDA seems to be
DISTSERV. I am not able to find this plan in Sysibm.sysplan.

Sibimon Philip
972-702-2515 - Office
972-417-3597 - Residence
E-mail - [login to unmask email]


-----Original Message-----
From: craig patton [mailto:[login to unmask email]
Sent: Tuesday, December 14, 1999 1:56 PM
To: [login to unmask email]
Subject: Re: DRDA re-bind problem


Philip,

What values in the BIND were specified for Connect/Disconnect? If defined
as EXPLICIT, and the application is NOT specifying DISCONNECT, I believe the
thread would stay active until a timeout threshold (if defined).

HTH
Craig Patton
DB2 DBA


>From: "Philip, Sibimon" <[login to unmask email]>
>Reply-To: DB2 Data Base Discussion List <[login to unmask email]>
>To: [login to unmask email]
>Subject: DRDA re-bind problem
>Date: Tue, 14 Dec 1999 14:34:57 -0500
>
>We are testing DRDA from SQLserver using Grandview ODBC driver to DB2 V5.1
>on OS/390 V2.6. After I execute the package from client/server, it looks
>like the thread is still active. Display thread shows as follows
>
>DSNV401I = DISPLAY THREAD REPORT FOLLOWS -
>DSNV402I = ACTIVE THREADS -
>NAME ST A REQ ID AUTHID PLAN ASID TOKEN
>SERVER RA * 7 ws-dal-l3728 L3728 DISTSERV 004A 26342
> V437-WORKSTATION=SYSB, USERID=l3728 ,
> APPLICATION NAME=ws-dal-l3728_317_l3728
> V445-SEANETA.JBDX.07CF0C0E2646=26342 ACCESSING DATA FOR <JBDX>:JBDX
> V447--LOCATION SESSID A ST TIME
> V448--<JBDX> F0000000000017EC W R2 9934814191741
>DISPLAY ACTIVE REPORT COMPLETE
>DSN9022I = DSNVDT '-DIS THREAD' NORMAL COMPLETION
>***
>Even though I got the result back, since this thread is active, I am not
>able to re-bind this package in DB2I in mainframe.The re-bind is telling,
>the resource is unavailable. My question is why this thread is active even
>after the completion of the execution. I appreciate if anybody knows the
>reason and solution for this.
>
>thanks
>Sibimon Philip
>972-702-2515 - Office
>972-417-3597 - Residence
>E-mail - [login to unmask email]
>
>
>
>
>

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


the








Sibimon Philip

Re: DRDA re-bind problem
(in response to Kurt Sahlberg)
When you display thread it shows the plan as DISTSERV. I do not know how it
got. I think the thread is active in DB2 because of DDF ZPARM
CMTSTAT=ACTIVE.

-DIS thread(*) loc(*) detail shows as follows

>DSNV401I = DISPLAY THREAD REPORT FOLLOWS -
>DSNV402I = ACTIVE THREADS -
>NAME ST A REQ ID AUTHID PLAN ASID TOKEN
>SERVER RA * 7 ws-dal-l3728 L3728 DISTSERV 004A 26342
> V437-WORKSTATION=SYSB, USERID=l3728 ,
> APPLICATION NAME=ws-dal-l3728_317_l3728
> V445-SEANETA.JBDX.07CF0C0E2646=26342 ACCESSING DATA FOR <JBDX>:JBDX
> V447--LOCATION SESSID A ST TIME
> V448--<JBDX> F0000000000017EC W R2 9934814191741
>DISPLAY ACTIVE REPORT COMPLETE
>DSN9022I = DSNVDT '-DIS THREAD' NORMAL COMPLETION


Thanks
Sibimon Philip
972-702-2515 - Office
972-417-3597 - Residence
E-mail - [login to unmask email]


-----Original Message-----
From: Kurt Sahlberg [mailto:[login to unmask email]
Sent: Wednesday, December 15, 1999 1:23 PM
To: [login to unmask email]
Subject: Re: DRDA re-bind problem


DRDA uses packages not plans check sysibm.syspackage.
Kurt


>>> "Philip, Sibimon" <[login to unmask email]> 12/15/99 12:12PM >>>
Craig,

The Disconnect is parameter for plan and the plan name for DRDA seems to be
DISTSERV. I am not able to find this plan in Sysibm.sysplan.

Sibimon Philip
972-702-2515 - Office
972-417-3597 - Residence
E-mail - [login to unmask email]


-----Original Message-----
From: craig patton [mailto:[login to unmask email]
Sent: Tuesday, December 14, 1999 1:56 PM
To: [login to unmask email]
Subject: Re: DRDA re-bind problem


Philip,

What values in the BIND were specified for Connect/Disconnect? If defined
as EXPLICIT, and the application is NOT specifying DISCONNECT, I believe the
thread would stay active until a timeout threshold (if defined).

HTH
Craig Patton
DB2 DBA


>From: "Philip, Sibimon" <[login to unmask email]>
>Reply-To: DB2 Data Base Discussion List <[login to unmask email]>
>To: [login to unmask email]
>Subject: DRDA re-bind problem
>Date: Tue, 14 Dec 1999 14:34:57 -0500
>
>We are testing DRDA from SQLserver using Grandview ODBC driver to DB2 V5.1
>on OS/390 V2.6. After I execute the package from client/server, it looks
>like the thread is still active. Display thread shows as follows
>
>DSNV401I = DISPLAY THREAD REPORT FOLLOWS -
>DSNV402I = ACTIVE THREADS -
>NAME ST A REQ ID AUTHID PLAN ASID TOKEN
>SERVER RA * 7 ws-dal-l3728 L3728 DISTSERV 004A 26342
> V437-WORKSTATION=SYSB, USERID=l3728 ,
> APPLICATION NAME=ws-dal-l3728_317_l3728
> V445-SEANETA.JBDX.07CF0C0E2646=26342 ACCESSING DATA FOR <JBDX>:JBDX
> V447--LOCATION SESSID A ST TIME
> V448--<JBDX> F0000000000017EC W R2 9934814191741
>DISPLAY ACTIVE REPORT COMPLETE
>DSN9022I = DSNVDT '-DIS THREAD' NORMAL COMPLETION
>***
>Even though I got the result back, since this thread is active, I am not
>able to re-bind this package in DB2I in mainframe.The re-bind is telling,
>the resource is unavailable. My question is why this thread is active even
>after the completion of the execution. I appreciate if anybody knows the
>reason and solution for this.
>
>thanks
>Sibimon Philip
>972-702-2515 - Office
>972-417-3597 - Residence
>E-mail - [login to unmask email]
>
>
>
>
>

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com













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



Kurt Sahlberg

Re: DRDA re-bind problem
(in response to Sibimon Philip)
Sibimon Philip wrote

1. When you display thread it shows the plan as DISTSERV. I do not
know how it got

From the DB2 V5 Admin Guide Classifying DDF Threads

PN The DB2 plan name associated with the DDF server thread. For DB2
private protocol requesters and DB2 DRDA requesters that are at
Version 3 or subsequent releases, this is the DB2 plan name of the
requesting application. For other DRDA requesters, you would use
'DISTSERV' for PN.

Look at 4.2.9.2.2 in DB2 V5 Admin Guide it describes the output
of the display thread command.

2. I think the thread is active in DB2 because of DDF ZPARM
CMTSTAT=ACTIVE.

Yes if you set CMTSTAT=INACTIVE your thread will go inactive after
you commit.
HTH
Kurt




>>> "Philip, Sibimon" <[login to unmask email]> 12/15/99 02:29PM >>>
When you display thread it shows the plan as DISTSERV. I do not know how it
got. I think the thread is active in DB2 because of DDF ZPARM
CMTSTAT=ACTIVE.

-DIS thread(*) loc(*) detail shows as follows

>DSNV401I = DISPLAY THREAD REPORT FOLLOWS -
>DSNV402I = ACTIVE THREADS -
>NAME ST A REQ ID AUTHID PLAN ASID TOKEN
>SERVER RA * 7 ws-dal-l3728 L3728 DISTSERV 004A 26342
> V437-WORKSTATION=SYSB, USERID=l3728 ,
> APPLICATION NAME=ws-dal-l3728_317_l3728
> V445-SEANETA.JBDX.07CF0C0E2646=26342 ACCESSING DATA FOR <JBDX>:JBDX
> V447--LOCATION SESSID A ST TIME
> V448--<JBDX> F0000000000017EC W R2 9934814191741
>DISPLAY ACTIVE REPORT COMPLETE
>DSN9022I = DSNVDT '-DIS THREAD' NORMAL COMPLETION


Thanks
972-702-2515 - Office
972-417-3597 - Residence
E-mail - [login to unmask email]


-----Original Message-----
From: Kurt Sahlberg [mailto:[login to unmask email]
Sent: Wednesday, December 15, 1999 1:23 PM
To: [login to unmask email]
Subject: Re: DRDA re-bind problem


DRDA uses packages not plans check sysibm.syspackage.
Kurt


>>> "Philip, Sibimon" <[login to unmask email]> 12/15/99 12:12PM >>>
Craig,

The Disconnect is parameter for plan and the plan name for DRDA seems to be
DISTSERV. I am not able to find this plan in Sysibm.sysplan.

Sibimon Philip
972-702-2515 - Office
972-417-3597 - Residence
E-mail - [login to unmask email]


-----Original Message-----
From: craig patton [mailto:[login to unmask email]
Sent: Tuesday, December 14, 1999 1:56 PM
To: [login to unmask email]
Subject: Re: DRDA re-bind problem


Philip,

What values in the BIND were specified for Connect/Disconnect? If defined
as EXPLICIT, and the application is NOT specifying DISCONNECT, I believe the
thread would stay active until a timeout threshold (if defined).

HTH
Craig Patton
DB2 DBA


>From: "Philip, Sibimon" <[login to unmask email]>
>Reply-To: DB2 Data Base Discussion List <[login to unmask email]>
>To: [login to unmask email]
>Subject: DRDA re-bind problem
>Date: Tue, 14 Dec 1999 14:34:57 -0500
>
>We are testing DRDA from SQLserver using Grandview ODBC driver to DB2 V5.1
>on OS/390 V2.6. After I execute the package from client/server, it looks
>like the thread is still active. Display thread shows as follows
>
>DSNV401I = DISPLAY THREAD REPORT FOLLOWS -
>DSNV402I = ACTIVE THREADS -
>NAME ST A REQ ID AUTHID PLAN ASID TOKEN
>SERVER RA * 7 ws-dal-l3728 L3728 DISTSERV 004A 26342
> V437-WORKSTATION=SYSB, USERID=l3728 ,
> APPLICATION NAME=ws-dal-l3728_317_l3728
> V445-SEANETA.JBDX.07CF0C0E2646=26342 ACCESSING DATA FOR <JBDX>:JBDX
> V447--LOCATION SESSID A ST TIME
> V448--<JBDX> F0000000000017EC W R2 9934814191741
>DISPLAY ACTIVE REPORT COMPLETE
>DSN9022I = DSNVDT '-DIS THREAD' NORMAL COMPLETION
>***
>Even though I got the result back, since this thread is active, I am not
>able to re-bind this package in DB2I in mainframe.The re-bind is telling,
>the resource is unavailable. My question is why this thread is active even
>after the completion of the execution. I appreciate if anybody knows the
>reason and solution for this.
>
>thanks
>Sibimon Philip
>972-702-2515 - Office
>972-417-3597 - Residence
>E-mail - [login to unmask email]
>
>
>
>
>

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


the




the





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