Item Subject: cc:Mail Text

     >From:    Jim Phillips <[log in to unmask]>

     >On Mon, 24 Mar 1997 20:39:54 -0800, Mark Boyd <[log in to unmask]>
     >writes:

     >>Has anyone heard of a rumored undocumented 'locklevel' command in
     >>dbutil?  I'd appreciate any information you could provide.

     >Well, I never heard of this before now, but by texting in
     >DBUTIL.PUB.SYS into my favorite editor, I located a string
     >"LOCKSIZELEVEL" in amongst the CIUPDATE, BUFFSPECS, etc.  which led
     >me to believe it's part of the SET command.  However, HELP SET does
     >not show anything about it.  So, on my test data base, I entered SET
     >DB1 LOCKSIZELEVEL and received "Invalid delimiter" in return.
     >Guessing LOCKSIZELEVEL to be numeric, I then entered SET DB1
     >LOCKSIZELEVEL=1, and got back "Locksizelevel set to 1".  Hmmmmm.
     >That "worked", but what's the "normal" value?  Well, a SHOW DB2 ALL
     >does not show the LOCKSIZELEVEL; however, a SHOW DB2 LOCKSIZELEVEL
     >does indeed return a value of 6.  So, I SET DB1 LOCKSIZELEVEL=6 and
     >that's all I know.

     I provide pre-sales support for HP sales reps(yes, they still do
     exist) and, as such, am not a database or programming guru as many of
     you are(...just setting up my firewall to prevent any too technical
     questions bouncing back).  However, I have been able to ascertain the
     following:

     The LOCKSIZELEVEL apparently deals with the lock area size of the DBG.
     The default value appears to be 6(six), with acceptable values of
     1(one) through 50(fifty).  Each level increment is good for about 100
     DBOPENs and 300 PREDICATE locks.  Without locking, each level is good
     for about 1000 DBOPENs.

     The tradeoff appears to be that the DBG is in SR6/7 space and
     increasing too much will fill it up(SR6/7 space).

     Jon Broz
     HP Cleveland
     [log in to unmask]
     (My opinions, right or wrong, are still mine...not HP's)