HP3000-L Archives

April 1997, Week 1

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:
Michele Conant <[log in to unmask]>
Reply To:
Date:
Wed, 2 Apr 1997 13:04:04 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
     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 have heard of this truly 'undocumented' command. It is undocumented
because 99% of HP3000 users will never use it. Though it is available in DBUTIL
using the SET command. The only time you would want to change the 'default of 6'
is if you get the message "DBG FULL ERROR".
The DBG file is where the database 'LOCKTABLE' resides. The maximum
LOCKSIZELEVEL is 50. The DBG 'LOCKSIZETABLE' is calculated by:

        Each level has by default 100 DBOPENS and 300 predicate locks.

So, by 'default of 6' you have at each level 600 DBOPENS and 1800 PREDICATE
LOCKS available on each database. That's truly alot of locking. If you changed
the LOCKSIZETABLE to 1, you would only have available at each level 100 DBOPENS
and 300 PREDICATE LOCKS.

Hope this helps, ;>

Michele Conant
E-mail: [log in to unmask]


______________________________ Reply Separator _________________________________
Subject: Re: Dbutil
Author:  <[log in to unmask] (Jim Phillips)> at internet
Date:    3/25/97 11:45 AM


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.

Hope this helps.  I'm sure someone more knowledgable than I will chime in
with the inside skinny.

Jim Phillips                            Manager of Information Systems
E-Mail: [log in to unmask]      Therm-O-Link, Inc.
Phone: (330) 527-2124                   P. O. Box 285
  Fax: (330) 527-2123                   Garrettsville, Ohio  44231

ATOM RSS1 RSS2