Glenn sez:

> ..... I had no idea that DBUTIL had this report available...
> and I don't even have to be in the same group as the
> database to use it!

AFAIK (meaning I didn't take time to try all of them myself
(left as exercise for the reader) ), the database name can
be fully qualified for all 15 choices for the DBUTIL SHOW
command (assuming of course that you have MPE access
to the group the database resides in)....

> Don't tell me DBUTIL is becoming *friendly* !? ;)

It's getting better...     :-)

> Clearly, I have (yet more) reading to do.  (First stop:  find out
> what the heck a "dependency semaphore" [DSEM] is.)

I refer Glenn and all who are interested to pages 10-8 and
10-9 of the August 1997 Sixth Edition of the TurboIMAGE/XL
DBMS Reference Manual.  It has a very nice two-page
description of DSEM.   Very short summary:  There used to
be only one PUTDELETE semaphore per database, to
protect the structural integrity of the database for execution
of DBPUT, DBDELETE, and DBUPDATE (with CIUPDATE
= ON

SIDEBAR # 1:  You *do* all have CIUPDATE = ON, right ??

SIDEBAR # 2:  You *do* have the August '97 edition of the
IMAGE manual, right ??

For scaling on high-end, multi-processor machines, this was
becoming a bottleneck.  Solution:  Assign one semaphore to
each dataset.  With DSEM ENABLEd, IMAGE can now lock
the semaphores for multiple independent Master - Detail
groups of datasets.  Throughput improvement will vary,
depending on the number of independent datasets groups
your database has;  and distribution of OLTP load across
those groups...   see again the manual, for a lot more detail.

DSEM was first available in TurboIMAGE version C.07.00.

Ken Sletten