DB2v7 z/OS: CMTSTAT ACTIVE/INACTIVE

Colin M Fay

DB2v7 z/OS: CMTSTAT ACTIVE/INACTIVE

Hi,

I have several modest-sized DB2 subsystems with these thread-related
ZPARM Settings like these:


FACCMST/DSN6FAC/CMTSTAT/DSNTIPR/ 7/DDF THREADS/ACTIVE


FACTCPAV/DSN6FAC/TCPALVER/DSNTIP5/ 3/TCP IP ALREADY VERIFIED/NO


FACRESYC/DSN6FAC/RESYNC/DSNTIPR/ 6/RESYNC INTERVAL/00002


FACRLFER/DSN6FAC/RLFERRD/DSNTIPR/ 5/RLST ACCESS ERROR /0000102060


FACSTART/DSN6FAC/DDF/DSNTIPR/ 1/DDF STARTUP OPTION/AUTO


FACTOIN/DSN6FAC/IDTHTOIN/DSNTIPR/10/IDLE THREAD TIMEOUT/00000


FACMAX1/DSN6FAC/MAXTYPE1/DSNTIPR/ 8/MAX TYPE1 INACTIVE
THREADS/0000000000

FACTCKA/DSN6FAC/TCPKPALV/DSNTIP5/ 8/TCPIP KEEPALIVE/ENABLE


FACINAC/DSN6FAC/POOLINAC/DSNTIP5/ 9/POOL THREAD TIMEOUT/00120





I would like to switch to CMTSTAT to INACTIVE , IDTHTOIN to 1800


1. Is there any other adjustments that should be made?
2. Are there any 'gotcha's' ?
3. Will this lead to inactive user's having to re-sign on after
they ,say, go to lunch for an hour?
4. Is there any way to measure the benefits of letting threads
go inactive?




Colin




_____



---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Kirk Hampton

Re: DB2v7 z/OS: CMTSTAT ACTIVE/INACTIVE
(in response to Colin M Fay)
Hi Colin,
I believe (and others here will correct me if I misspeak) that these
two parameters only deal with threads coming in via DDF. We have had
ours set to CMTSTAT=INACTIVE and IDTHTOIN=3600 (one hour) for many moons
now. What this does is make any distributed thread that connects and
starts a unit of work (ACTIVE) then, due to some problem at the remote
end, does nothing for one hour, the thread will then time out and the
unfinished work will be rolled back. DDF threads that connect but either
do not start a unit of work, or complete one correctly by issuing a
COMMIT, will go INACTIVE, and can stay connected as long as they like,
while they go to lunch or whatever. Having it set they way you
currently do means that all DDF threads stay active forever, which
counts against your MAXDBAT number.

Kirk Hampton
DB2 z/OS Sysprog
IBM Certified Database Administrator - DB2 UDB V8.1 for z/OS
Capgemini Energy
Dallas, Texas

________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Fay, Colin M
Sent: Friday, December 16, 2005 7:32 AM
To: [login to unmask email]
Subject: Re: [DB2-L] DB2v7 z/OS: CMTSTAT ACTIVE/INACTIVE



Hi,

I have several modest-sized DB2 subsystems with these thread-related
ZPARM Settings like these:


FACCMST/DSN6FAC/CMTSTAT/DSNTIPR/ 7/DDF THREADS/ACTIVE


FACTCPAV/DSN6FAC/TCPALVER/DSNTIP5/ 3/TCP IP ALREADY VERIFIED/NO


FACRESYC/DSN6FAC/RESYNC/DSNTIPR/ 6/RESYNC INTERVAL/00002


FACRLFER/DSN6FAC/RLFERRD/DSNTIPR/ 5/RLST ACCESS ERROR /0000102060


FACSTART/DSN6FAC/DDF/DSNTIPR/ 1/DDF STARTUP OPTION/AUTO


FACTOIN/DSN6FAC/IDTHTOIN/DSNTIPR/10/IDLE THREAD TIMEOUT/00000


FACMAX1/DSN6FAC/MAXTYPE1/DSNTIPR/ 8/MAX TYPE1 INACTIVE
THREADS/0000000000

FACTCKA/DSN6FAC/TCPKPALV/DSNTIP5/ 8/TCPIP KEEPALIVE/ENABLE


FACINAC/DSN6FAC/POOLINAC/DSNTIP5/ 9/POOL THREAD TIMEOUT/00120





I would like to switch to CMTSTAT to INACTIVE , IDTHTOIN to 1800


1. Is there any other adjustments that should be made?
2. Are there any 'gotcha's' ?
3. Will this lead to inactive user's having to re-sign on after
they ,say, go to lunch for an hour?
4. Is there any way to measure the benefits of letting threads
go inactive?




Colin




________________________________


------------------------------------------------------------------------
--------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the
archives and home page at http://www.idugdb2-l.org/archives/db2-l.html.
From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Martin Packer

Re: DB2v7 z/OS: CMTSTAT ACTIVE/INACTIVE
(in response to Kirk Hampton)
... and one aspect of why it's OK to allow inactive threads to lie around
is that their memory footprint is very small. In a recent client engagement
I saw (from IFCID 225) a Siebel application's threads averaging under 100K.
And most of that time was in in the "thread gone inactive" state.

Cheers, Martin

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

"Next time someone says a penny for your thoughts - sell!" Peter Kay, Hyde
Park, July 15, 2005

External Blog:
http://www-128.ibm.com/developerworks/blogs/dw_blog.jspa?blog=476
Internal Blog:
http://[login to unmask email]

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Colin M Fay

Re: DB2v7 z/OS: CMTSTAT ACTIVE/INACTIVE
(in response to Martin Packer)
Hi Kirk and Martin,

Thanks, that was just the re-assurance I needed. It sounds
straightforward, I dont know why it wasn't done here before.



Colin

_____

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Kirk Hampton
Sent: Monday, December 19, 2005 5:45 PM
To: [login to unmask email]
Subject: Re: [DB2-L] DB2v7 z/OS: CMTSTAT ACTIVE/INACTIVE


Hi Colin,
I believe (and others here will correct me if I misspeak) that these
two parameters only deal with threads coming in via DDF. We have had
ours set to CMTSTAT=INACTIVE and IDTHTOIN=3600 (one hour) for many moons
now. What this does is make any distributed thread that connects and
starts a unit of work (ACTIVE) then, due to some problem at the remote
end, does nothing for one hour, the thread will then time out and the
unfinished work will be rolled back. DDF threads that connect but either
do not start a unit of work, or complete one correctly by issuing a
COMMIT, will go INACTIVE, and can stay connected as long as they like,
while they go to lunch or whatever. Having it set they way you
currently do means that all DDF threads stay active forever, which
counts against your MAXDBAT number.

Kirk Hampton
DB2 z/OS Sysprog
IBM Certified Database Administrator - DB2 UDB V8.1 for z/OS
Capgemini Energy
Dallas, Texas

_____

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Fay, Colin M
Sent: Friday, December 16, 2005 7:32 AM
To: [login to unmask email]
Subject: Re: [DB2-L] DB2v7 z/OS: CMTSTAT ACTIVE/INACTIVE



Hi,

I have several modest-sized DB2 subsystems with these thread-related
ZPARM Settings like these:


FACCMST/DSN6FAC/CMTSTAT/DSNTIPR/ 7/DDF THREADS/ACTIVE


FACTCPAV/DSN6FAC/TCPALVER/DSNTIP5/ 3/TCP IP ALREADY VERIFIED/NO


FACRESYC/DSN6FAC/RESYNC/DSNTIPR/ 6/RESYNC INTERVAL/00002


FACRLFER/DSN6FAC/RLFERRD/DSNTIPR/ 5/RLST ACCESS ERROR /0000102060


FACSTART/DSN6FAC/DDF/DSNTIPR/ 1/DDF STARTUP OPTION/AUTO


FACTOIN/DSN6FAC/IDTHTOIN/DSNTIPR/10/IDLE THREAD TIMEOUT/00000


FACMAX1/DSN6FAC/MAXTYPE1/DSNTIPR/ 8/MAX TYPE1 INACTIVE
THREADS/0000000000

FACTCKA/DSN6FAC/TCPKPALV/DSNTIP5/ 8/TCPIP KEEPALIVE/ENABLE


FACINAC/DSN6FAC/POOLINAC/DSNTIP5/ 9/POOL THREAD TIMEOUT/00120





I would like to switch to CMTSTAT to INACTIVE , IDTHTOIN to 1800


1. Is there any other adjustments that should be made?
2. Are there any 'gotcha's' ?
3. Will this lead to inactive user's having to re-sign on after
they ,say, go to lunch for an hour?
4. Is there any way to measure the benefits of letting threads
go inactive?




Colin




_____


------------------------------------------------------------------------
--------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the
archives and home page at http://www.idugdb2-l.org/archives/db2-l.html.
From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm
------------------------------------------------------------------------
--------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the
archives and home page at http://www.idugdb2-l.org/archives/db2-l.html.
From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm