PeopleSoft active threads.

Glenn Mackey

PeopleSoft active threads.
Hi,
(I posted this to 2 groups, DB2 and PeopleSoft)

My problem/question is that we have active DDF threads from PeopleSoft V8x
connected always. I would like to know if other sites have the same
situation, solved it or what. I want them to go inactive.

We have installed PeopleSoft V8.1.8 with HR 8.3 into an OS390 DB2 V6.1
environment.
The NT application server (Tuxedo) and process scheduler (NT) have the
active threads all the time. I did a trace and no commits are done to send
the threads to an inactive state.

The Tuxedo and process scheduler (NT) processes allocating the threads are
...


psdstsrv.exe
PSSUBDSP.exe
PSPUBDSP.exe
PSBRKDSP.exe

PSBRKHND.exe
PSBRKDSP.exe
PSBRKHND.exe
PSSUBDSP.exe

The pertinent parameters we have to control this

zparm
cmstat=inactive
idthtoin=0
relcurhl=yes

poolinac=120

DB2Connect EE V7.2 fp7.
cursorhold is enabled


Thanks
Glenn Mackey
Database Administration
GuideOne Insurance
Phone: 515.267.5767
Pager: 515.241.1627



Martin Packer

Re: PeopleSoft active threads.
(in response to Glenn Mackey)
Just specifying CMTSTAT=INACTIVE doesn't necessarily make all threads go
inactive. There are some restrictions. Some of these are resolved with Type
2 Inactive threads, which were introduced with Version 6 - your release.

(You didn't state whether ZPARM had MAXTYPE1=0 to force Type 2 Inactive
Threads or not so you may not be aware of Type 2 Inactive threads. Of
course, MAXTYPE1=0 isn't necessary for the subsystem to try Type 2.)

Regards, Martin

Martin Packer, MBCS Martin Packer/UK/IBM
020-8832-5167 in the UK (+44) (MOBX 273643, Internal 7-325167, Mobile
07802-245584)



"Mackey, Glenn"
<[login to unmask email] To: [login to unmask email]
L.COM> cc:
Sent by: DB2 Data Subject: PeopleSoft active threads.
Base Discussion
List
<[login to unmask email]
LASSOC.COM>


08-01-03 16:12
Please respond to
DB2 Data Base
Discussion List





Hi,
(I posted this to 2 groups, DB2 and PeopleSoft)

My problem/question is that we have active DDF threads from PeopleSoft V8x
connected always. I would like to know if other sites have the same
situation, solved it or what. I want them to go inactive.

We have installed PeopleSoft V8.1.8 with HR 8.3 into an OS390 DB2 V6.1
environment.
The NT application server (Tuxedo) and process scheduler (NT) have the
active threads all the time. I did a trace and no commits are done to send
the threads to an inactive state.

The Tuxedo and process scheduler (NT) processes allocating the threads are
...


psdstsrv.exe
PSSUBDSP.exe
PSPUBDSP.exe
PSBRKDSP.exe

PSBRKHND.exe
PSBRKDSP.exe
PSBRKHND.exe
PSSUBDSP.exe

The pertinent parameters we have to control this

zparm
cmstat=inactive
idthtoin=0
relcurhl=yes

poolinac=120

DB2Connect EE V7.2 fp7.
cursorhold is enabled


Thanks
Glenn Mackey
Database Administration
GuideOne Insurance
Phone: 515.267.5767
Pager: 515.241.1627



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



Venkatesh Mokshagundam

Re: PeopleSoft active threads.
(in response to Martin Packer)
Glenn, you have idthtoin=0.

You may have to change this to some value. We have set at 3600 (see
description of this ZPARM from DB2 Manuals below).

FYI....we do not have Peoplesoft, but we do use DDF.

Specifying 0 disables timeout processing. If you accept the default value,
0, DB2 continues to operate as it did prior to DB2 Version 7. (Idle server
threads remain in the system and continue to hold their resources, if any.)

HTH,

Venkatesh Mokshagundam
Database Administrator
Corporate Systems,
Amarillo, TX 79102
Ph: 806-337-3374
Fax: 806-345-2736


-----Original Message-----
From: Martin Packer [mailto:[login to unmask email]
Sent: Wednesday, January 08, 2003 11:05 AM
To: [login to unmask email]
Subject: Re: PeopleSoft active threads.


Just specifying CMTSTAT=INACTIVE doesn't necessarily make all threads go
inactive. There are some restrictions. Some of these are resolved with Type
2 Inactive threads, which were introduced with Version 6 - your release.

(You didn't state whether ZPARM had MAXTYPE1=0 to force Type 2 Inactive
Threads or not so you may not be aware of Type 2 Inactive threads. Of
course, MAXTYPE1=0 isn't necessary for the subsystem to try Type 2.)

Regards, Martin

Martin Packer, MBCS Martin Packer/UK/IBM
020-8832-5167 in the UK (+44) (MOBX 273643, Internal 7-325167, Mobile
07802-245584)



"Mackey, Glenn"
<[login to unmask email] To:
[login to unmask email]
L.COM> cc:
Sent by: DB2 Data Subject: PeopleSoft active
threads.
Base Discussion
List
<[login to unmask email]
LASSOC.COM>


08-01-03 16:12
Please respond to
DB2 Data Base
Discussion List





Hi,
(I posted this to 2 groups, DB2 and PeopleSoft)

My problem/question is that we have active DDF threads from PeopleSoft V8x
connected always. I would like to know if other sites have the same
situation, solved it or what. I want them to go inactive.

We have installed PeopleSoft V8.1.8 with HR 8.3 into an OS390 DB2 V6.1
environment.
The NT application server (Tuxedo) and process scheduler (NT) have the
active threads all the time. I did a trace and no commits are done to send
the threads to an inactive state.

The Tuxedo and process scheduler (NT) processes allocating the threads are
...


psdstsrv.exe
PSSUBDSP.exe
PSPUBDSP.exe
PSBRKDSP.exe

PSBRKHND.exe
PSBRKDSP.exe
PSBRKHND.exe
PSSUBDSP.exe

The pertinent parameters we have to control this

zparm
cmstat=inactive
idthtoin=0
relcurhl=yes

poolinac=120

DB2Connect EE V7.2 fp7.
cursorhold is enabled


Thanks
Glenn Mackey
Database Administration
GuideOne Insurance
Phone: 515.267.5767
Pager: 515.241.1627



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








The information contained in this communication,
including attachments, is strictly confidential
and for the intended use of the addressee only;
it may also contain proprietary, price sensitive,
or legally privileged information. Notice is
hereby given that any disclosure, distribution,
dissemination, use, or copying of the information
by anyone other than the intended recipient is
strictly prohibited and may be illegal. If you
have received this communication in error, please
notify the sender immediately by reply e-mail, delete
this communication, and destroy all copies.


Corporate Systems, Inc. has taken reasonable precautions
to ensure that any attachment to this e-mail has been
swept for viruses. We specifically disclaim all liability
and will accept no responsibility for any damage sustained
as a result of software viruses and advise you to carry out
your own virus checks before opening any attachment.



Venkatesh Mokshagundam

Re: PeopleSoft active threads.
(in response to Venkatesh Mokshagundam)
Sorry, I didn't notice you were on V6.1. My reply may not apply in your
case.

-----Original Message-----
From: Venkatesh Mokshagundam
Sent: Wednesday, January 08, 2003 11:33 AM
To: 'DB2 Data Base Discussion List'
Subject: RE: PeopleSoft active threads.


Glenn, you have idthtoin=0.

You may have to change this to some value. We have set at 3600 (see
description of this ZPARM from DB2 Manuals below).

FYI....we do not have Peoplesoft, but we do use DDF.

Specifying 0 disables timeout processing. If you accept the default value,
0, DB2 continues to operate as it did prior to DB2 Version 7. (Idle server
threads remain in the system and continue to hold their resources, if any.)

HTH,

Venkatesh Mokshagundam
Database Administrator
Corporate Systems,
Amarillo, TX 79102
Ph: 806-337-3374
Fax: 806-345-2736


-----Original Message-----
From: Martin Packer [mailto:[login to unmask email]
Sent: Wednesday, January 08, 2003 11:05 AM
To: [login to unmask email]
Subject: Re: PeopleSoft active threads.


Just specifying CMTSTAT=INACTIVE doesn't necessarily make all threads go
inactive. There are some restrictions. Some of these are resolved with Type
2 Inactive threads, which were introduced with Version 6 - your release.

(You didn't state whether ZPARM had MAXTYPE1=0 to force Type 2 Inactive
Threads or not so you may not be aware of Type 2 Inactive threads. Of
course, MAXTYPE1=0 isn't necessary for the subsystem to try Type 2.)

Regards, Martin

Martin Packer, MBCS Martin Packer/UK/IBM
020-8832-5167 in the UK (+44) (MOBX 273643, Internal 7-325167, Mobile
07802-245584)



"Mackey, Glenn"
<[login to unmask email] To:
[login to unmask email]
L.COM> cc:
Sent by: DB2 Data Subject: PeopleSoft active
threads.
Base Discussion
List
<[login to unmask email]
LASSOC.COM>


08-01-03 16:12
Please respond to
DB2 Data Base
Discussion List





Hi,
(I posted this to 2 groups, DB2 and PeopleSoft)

My problem/question is that we have active DDF threads from PeopleSoft V8x
connected always. I would like to know if other sites have the same
situation, solved it or what. I want them to go inactive.

We have installed PeopleSoft V8.1.8 with HR 8.3 into an OS390 DB2 V6.1
environment.
The NT application server (Tuxedo) and process scheduler (NT) have the
active threads all the time. I did a trace and no commits are done to send
the threads to an inactive state.

The Tuxedo and process scheduler (NT) processes allocating the threads are
...


psdstsrv.exe
PSSUBDSP.exe
PSPUBDSP.exe
PSBRKDSP.exe

PSBRKHND.exe
PSBRKDSP.exe
PSBRKHND.exe
PSSUBDSP.exe

The pertinent parameters we have to control this

zparm
cmstat=inactive
idthtoin=0
relcurhl=yes

poolinac=120

DB2Connect EE V7.2 fp7.
cursorhold is enabled


Thanks
Glenn Mackey
Database Administration
GuideOne Insurance
Phone: 515.267.5767
Pager: 515.241.1627



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








The information contained in this communication,
including attachments, is strictly confidential
and for the intended use of the addressee only;
it may also contain proprietary, price sensitive,
or legally privileged information. Notice is
hereby given that any disclosure, distribution,
dissemination, use, or copying of the information
by anyone other than the intended recipient is
strictly prohibited and may be illegal. If you
have received this communication in error, please
notify the sender immediately by reply e-mail, delete
this communication, and destroy all copies.


Corporate Systems, Inc. has taken reasonable precautions
to ensure that any attachment to this e-mail has been
swept for viruses. We specifically disclaim all liability
and will accept no responsibility for any damage sustained
as a result of software viruses and advise you to carry out
your own virus checks before opening any attachment.



Bill Dwornikiewicz

Re: PeopleSoft active threads.
(in response to Venkatesh Mokshagundam)
We have IDTHTOIN set to 360 in our environment and it does not change =
anything. These peoplesoft threads are related to background processes =
related to message handling that wake up periodically (typically every 30 =
seconds) looking for work. When you cancel them they get restarted =
automatically. They only go away if you shut down the processes accociated =
with them. The threads are:
PSBRKDSP Publication Broker dispatcher (for application messaging).
PSBRKHND Publication broker handler (for application messaging).
PSSUBDSP Subscription contract dispatcher (for application messaging).
PSSUBHND Subscription contract handler (for application messaging).
PSPUBDSP Publication contract dispatcher (for application messaging).
PSPUBHND Publication contract handler (for application messaging).
=20


>>> [login to unmask email] 01/08/03 12:33PM >>>
Glenn, you have idthtoin=0.

You may have to change this to some value. We have set at 3600 (see
description of this ZPARM from DB2 Manuals below).

FYI....we do not have Peoplesoft, but we do use DDF.

Specifying 0 disables timeout processing. If you accept the default value,
0, DB2 continues to operate as it did prior to DB2 Version 7. (Idle server
threads remain in the system and continue to hold their resources, if any.)

HTH,

Venkatesh Mokshagundam
Database Administrator
Corporate Systems,
Amarillo, TX 79102
Ph: 806-337-3374
Fax: 806-345-2736