>>  Karl writes
>> Is there a way, either by a user or an HP Tech, to kill a looping process?
 
>> There is a session that apparently has a database locked and has looped
>> or hung.  DBUTIL shows the session as having the database locked and
>> also waiting for a lock.  Tried UNDEDLOK but it does not recognize that
>> perticular PIN as a deadlock candidate.If I put the PIN in UNDEDLOK,
>> it does nothing.
 
I don't have a solution to the problem after it occurs, perhaps other's may.
The cause of the problem may be the way the program is attempting to
obtain the lock.   If you are issuing a database lock and acquire the lock,
if an additional DBLOCK is issued to the base (Mode 2, 4, or 6) and fails
and the program continues to apply the lock until a status of 0 is returned,
the above situation occurs.  If the program applies a lock and then tries
to acquire an additional lock (Mode 1,3, or 5) the program doesn't loop but
you still have a deadlock.
 
I don't know that this is the problem but when it was stated
 
>> "DBUTIL shows the session as having the database locked and
>> also waiting for a lock."
 
the above scenario may apply.
 
Steve Cole
Outer Banks Solutions