2010/5/10 van Sleeuwen, Berry <[email protected]>: > Hello listers, > > We have (re)installed a SLES10 with DB2 connect 9.5. Our base SLES10 is > configured to drop out of queue when it is not active so these base > guests only enter Q1 at some regular intervals. But when we start DB2 it > remains in Q3. So it looks like there is some process that remains > active. Even when the DB2 connect itself is not (yet) connected to a zOS > database. The DB2 hardly uses any CPU, the guest uses only slightly more > than the base SLES10 guest. > > What can we do to let this guest go out of Q3 when it is not processing? > Are there any options within DB2 connect we can look at?
Are you sure you're doing the right thing there? It sounds like you've started a database instance rather than DB2 Connect. As Marcy points out, when you do want to run a DB2 instance there's a new option in DB2 9.7 FP1. Without that option an idle DB2 instance polls and stays in queue (it's still on my list to verify that the option fixes this). -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
