Chris,

  Did you happen to try the ISQL "TERMINATE USER" command?
After the system was brought back up, did you try it again, and if so,
what was the result?  The only time I've seen something like this before
was while the DBE was in the middle of a massive "and I do mean
MASSIVE" rollback.

Regards,
Michael L Gueterman
Easy Does It Technologies
email: [log in to unmask]
http://www.editcorp.com
voice: (509) 943-5108
fax:   (509) 946-1170
--

----------
From:  Chris Breemer[SMTP:[log in to unmask]]
Sent:  Friday, April 25, 1997 4:30 AM
To:  [log in to unmask]
Subject:  [HP3000-L] Allbase/MPE lockup

Hi all,

I have a client-server application that accesses an Albase database on the 3k.
The client locks up as soon as the server prog has connected to the database
(no other processes are connected to that database; the user has DBA rights on the
database). I can abort the client but
I can't get rid of the server job. The offending process is waiting on an 'sql lock'
(as reported by AIFPROCGET), and indeed with SQLMON I see quite a number of table locks,
like on DBCORE.MARSCH etc.
Whatever I try to abort the server job, it stays there. I've tried all variations of
abortjob/abortio/kill. MPE does not report any errors, just nothing changes.
I had to reboot my system to get rid of the job. Ugh.

<snip>