we are running db2 v822 on z/VM 5.1, under that OS we are runnign linux
sles9 sp3 the apps on linux are: WAS v51 and CM v8.3.00.100.


We are have a strange common occurence. When we start the apps up under
linux there are about 190 tasks with the majority being associated with
db2. The number of tasks climb to approx 270-280,again with most of those sleeping.
This consumes memeory and swap resources.
But on Fridays we shut the apps down and reboot the os as we must do backups .
When we bring the systems back DB2 has released the dbsysc processes and we start fresh.
BUT late last week one of ourtest servers won't release the dbsysc processes. So when it's restarted it comes back with the large numbers.

NO CHANGES HAVE BEEN MADE(or so I've been told)
Since it's a test server I'm not worried but if it can happen to one it could happen to a production guest which could prove fatal.
I've opened a pmr with IBM but haven't heard anything yet so I thought I'd try here.

*****After all app shutdown====DRW

top - 08:44:48 up 22:29, 2 users, load average: 1.26, 1.11, 0.65
Tasks: 64 total, 2 running, 61 sleeping, 0 stopped, 1 zombie
Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 99.3% id, 0.7% wa, 0.0% hi, 0.0% si
Mem: 723700k total, 140904k used, 582796k free, 9552k buffers
Swap: 1048936k total, 65188k used, 983748k free, 91560k cached

******After shutdown w/db2 up

top - 08:50:41 up 3 min, 1 user, load average: 1.80, 1.17, 0.46
Tasks: 176 total, 2 running, 174 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.3% us, 0.0% sy, 0.0% ni, 99.2% id, 0.3% wa, 0.0% hi, 0.2% si
Mem: 723700k total, 671516k used, 52184k free, 17000k buffers
Swap: 1048936k total, 0k used, 1048936k free, 271860k cached


+-db2sysc---db2sysc---db2fmp
¦ +-107*[db2sysc]
¦ +-db2sysc---13*[db2sysc]

**PSTREE from PRW after being up 1 day
+-db2sysc---db2sysc---4*[db2fmp]
¦ +-4*[db2sysc]
¦ +-db2sysc---31*[db2sysc]
¦ +-db2sysc---14*[db2sysc]
¦ +-db2sysc---db2sysc
¦ +-db2sysc---9*[db2sysc

**********after was/cm/server1 are up
top - 08:57:34 up 10 min, 1 user, load average: 0.93, 1.11, 0.65
Tasks: 261 total, 2 running, 259 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0% us, 0.3% sy, 0.0% ni, 99.7% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 723700k total, 713452k used, 10248k free, 9672k buffers
Swap: 1048936k total, 471728k used, 577208k free, 126168k cached
*******The above numbers are the same as when we started this test

thanks
Mace

have your shutdown process modified
do db2stop in instance owner : with force option
execute ipclean to kill all processes
there are also commands to shutdown the fault monitor for instance db2fm processes and fault monitor coordinating deamon db2fmc

Guy,
I thought you hit the nail on the head with the ipclean as we had to do that a long time ago. But after I did it and brought db2 back up it retruned with all the db2sysc process (107*[db2sysc]) When it should startup with no more than 25.
Anyother suggestions are appreciated
Mace