John Clogg writes:

Although Ken's point about the dangers of UNDEDLOK is well taken, the
potential damage is no worse, it would seem, than HALTing the system while
database accessors are deadlocked.  At least with UNDEDLOK you get to choose
which process dies, which may serve to mitigate the damage.  Still, it is
dangerous, and anytime you encounter a deadlock, you should take steps to
prevent its recurrence, rather than depending on UNDEDLOK.

Ken, I tried unsuccessfully to find the new version of UNDEDLOK on the ITRC.
A search on "UNDEDLOK" yielded nothing but some old documents.  Can you give
some more information about its location?
--------------------------------------------------
As I wrote earlier today, here are the patches.

Actually, the current version is A.70.00 which can be obtained by
6.0  NRCLXJ5A
6.5  NRCLXP0A
7.0  the patch NRCLXP0C does NOT contain UNDEDLOK, probably have to call HP

Mike Berkowitz
Guess? Inc.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *