Runaway dbaccess process

On our current application, users start dbaccess and sometimes disconnect without properly exiting (turning off terminal, etc.). The dbaccess process hangs and proceeds to take over ALL of CPU 1 or 2. When I do a top or sar, one of the CPUs is pegged by the dbaccess process! I was able to easily reproduce this by starting dbaccess, doing "select * from customer" and disconnecting. The process is eating CPU time but not Informix time. Neither the session nor the thread was accruing any reads or writes, but the process was chewing CPU like crazy. Here's the config: We're running HP-UX 10.20 with ODS 7.20. We have three CPUs and the following settings: NUMCPUVPS=1,SINGLE_CPU_VP=1,MULTIPROCESSOR=0 (I'm basing these settings on the rule of thumb about pretending like there's one CPU for anything less than 4. I'll tweak when I can get offline time). We're not currently using KAIO (waiting for HP patches). Nothing else exciting I can think of. My theory is that it relates to the Informix version and processor settings. Has anyone else experienced such a thing? Any ideas? Thanks, Ron Ron Flannery | President, rflanner@one-point.com | Michigan Informix User Group President, One Point Solutions| http://www.zenacomp.com/miug/ http://www.one-point.com voice=248.887.8470