HP3000-L Archives

December 2006, Week 3

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:
"Keven Miller (3kr)" <[log in to unmask]>
Reply To:
Keven Miller (3kr)
Date:
Wed, 20 Dec 2006 06:03:15 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
More info from Image manual, Chapter 4, Database Control Blocks

• The Database System Control Block (DBS) is created by DBOPEN if it does not already
exist. The DBS is used as a system-wide table to locate the current Database Globals
Control Block (DBG) for any opened database. Each system has only one DBS, created
as a permanent file called TURBODBS in the PUB group and the SYS account on that
system.

• The TurboLock Table is a permanent file, TURBOLKT.PUB.SYS, that is created by
DBOPEN (if it does not exist beforehand). Thereafter, it is opened when the first user
opens any database on the system. It is purged when the system is rebooted. Each
system has only one TURBOLKT file. It is used to avoid deadlocks for all IMAGE/SQL
users. Additionally, it is also used to detect potential deadlock for TurboIMAGE/XL
users if, and only if, deadlock detection is activated by DBCONTROL mode 7.

• The Global Dynamic Multi-database Transaction Table is a permanent file,
TURBOGTX.PUB.SYS, that is created by DBXBEGIN (if it does not exist beforehand).
Thereafter, it is opened for all users who employ dynamic multi-database transaction(s)
(DMDBX). Each system has only one TURBOGTX file, and it remains on the system even
after the system is rebooted. It is used for tracking DMDBX.


Keven
(searchable PDFs are nice)
(Why isn't the Image manual in HTML format at docs.hp.com?)

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2