Re: buffer specification in run.dbutil.pub.sys (266 Views)
Reply
Regular Advisor
Posts: 111
Registered: ‎12-28-1998
Message 1 of 6 (266 Views)

buffer specification in run.dbutil.pub.sys

Can anyone explain me the value setting on the
buffer spec in dbutil.pub.sys concerning about the database.

Currently in one of my database I have a setting like: Buffer specifications: 70(1/120)
and I have about 100 users on board. The impact currently that encounter is process deadlock.
Could anyone kindly advise me . Thank you.
Trusted Contributor
Posts: 178
Registered: ‎12-04-1997
Message 2 of 6 (266 Views)

Re: buffer specification in run.dbutil.pub.sys

Well, according to the image manual (appendix H-12) buffspecs is there for MPE/V comaptability only. The number of buffspecs is set to 1280 on TurboIMAGE/XL. I think something else is causing your process deadlock.

ps, is the deadlock an image deadlock or a process deadlock?

Ian Warner
Why did anyone invent unix?
Regular Advisor
Posts: 111
Registered: ‎12-28-1998
Message 3 of 6 (266 Views)

Re: buffer specification in run.dbutil.pub.sys

It is a process deadlock, upon running undedlok.prvxl.telesup, the lock is clear.
Regards,
Clarence

Trusted Contributor
Posts: 178
Registered: ‎12-04-1997
Message 4 of 6 (266 Views)

Re: buffer specification in run.dbutil.pub.sys

I would suggest checking the lock stategy within the calling programs, or doing a DBCONTROL mode 7 to check for a deadlock within the offending programs (this will return an error 26 instead of a process hang).

Ian Warner


Why did anyone invent unix?
Regular Advisor
Posts: 111
Registered: ‎12-28-1998
Message 5 of 6 (266 Views)

Re: buffer specification in run.dbutil.pub.sys

Thanks for your information.
Highlighted
Occasional Advisor
Posts: 6
Registered: ‎03-05-2001
Message 6 of 6 (266 Views)

Re: buffer specification in run.dbutil.pub.sys

the bufferspec is no longer used by image. The replacement for this is locksizelevel.

The note: KBAN00000399 has details. Basically
This can be used to increase the total number of locks that can be held
for the given database.

But increasing the value will increase the size of the DBG & hence of SR6/7 usage, so should not be done lightly. Look at the application design to see if the number of locks issued can be decreased. Each increase in "level" will increase the lockarea size by 16,384 16 bit words. LOCKSIZELEVEL 1 will give a lockarea size of 49,152 16 bit
words and each increase in LOCKSIZELEVEL will add 16,384 16 bit words to the lockarea.

As a rule, each LOCKSIZELEVEL will allow 100 DBOPENs with 300 predicate locks each. When running out of lockarea, you may see the following errors.

DBG Control Block Full -- Condition 62 returned by DBLOCK
DBG Control Block Full -- Condition -197 returned by DBOPEN

Locksizelevel replaces the option BUFFSPECS. See the TurboImage manual
appendix H for a description of this option.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.