HP3000-L Archives

November 1996, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jerry Fochtman <[log in to unmask]>
Reply To:
Jerry Fochtman <[log in to unmask]>
Date:
Fri, 22 Nov 1996 16:59:29 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines)
At 11:58 AM 11/18/96 CST, Craig Vespe wrote:
>Jim Phillips writes -
>[...]
>>
>>For some years, there has been a request in the HP3K user community
>>for HP to provide a way of resolving 'deadly embraces'.  The only
>>way I know of resolving a true 'deadly embrace' is to re-boot the
>>system, so if we can use DBUTIL to resolve it, I would be interested
>>in knowing how.  Thanks.
>>
>   I believe UNDEDLOK.PRVXL.TELESUP can resolve 'deadly embraces',
>   and thus the item has been taken off the SIG-IMAGE list.

In the 5.5 communicator HP has documented several of the newer modes for
DBCONTROL.  On page 6-66 the article indicates that mode 7 also activates
the database for deadlock detection.  If I recall earlier discussions on
this, there is additional overhead in performing the analysis in order to
detect the deadlock and because of this, the feature was enabled by default.

/jf

ATOM RSS1 RSS2