Article 168720 of comp.os.vms:
In article <1997Apr30.193839.1@eisner>, schenkenberg@eisner.decus.org (Brian Schenkenberger, VAXman-) writes:
> In article <33678D35.7F0A@cisco.com>, Jim Mehlhop <jmehlhop@cisco.com> writes:
>> Looking for a quick answer to avoid looking it up myself.  Does anyone
>> remember the sysgen parameter and bit settings to control lock
>> re-mastering in a cluster??

> You're looking for LOCKDIRWT but it's not a bit setting.  Rather, it's
> a weighting factor in the arbitration scheme for the resourses.  

Well, there's the PE1 parameter, which limits the size of lock trees which
will be dynamically remastered.  If you have a database which uses enormous
lock trees, and if you from time to time have the supposedly rare database hangs
which can occur for some unknown reason during remastering, it is sometimes
recommended you change this from the default of 0 (unlimited) to a value of
100.

--
George Cornelius              cornelius@eisner.decus.org
                              cornelius@mayo.edu