HP3000-L Archives

March 1997, 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:
Jim Phillips <[log in to unmask]>
Reply To:
Jim Phillips <[log in to unmask]>
Date:
Tue, 25 Mar 1997 11:45:59 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 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 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