We've run multiple databases per logging process for years, but I've never
been able to successfully resolve the number of write-mode opens on the
databases with the reported number of users per logid (:SHOWLOGSTATUS).
For example, I look at the four databases using one logid in DBUTIL, and
the number of users (all mode-1 opens) opening all four databases is
reported as 617; however :SHOWLOGSTATUS reports 199 users against the logid
associated with the databases.  One database does show the same number of
opens as is reported by :SHOWLOGSTATUS, and this database is always opened
by this application for security processing, but the other three db's are
not opened until needed.  The other logging processes on the system each
have only one database associated with them, and the number of
DBUTIL-reported opens does match the number of users counted for each logid
via :SHOWLOGSTATUS.  Therefore, I'm reasonably certain that the
users-per-logid count is incremented only for an open on the first of 'n'
databases associated with that logid, but this is only a rough assumption.

At peak usage, the most heavily used logid shows about 700+ users.

One other note:  I just discovered that DBUTIL now allows a REDO command.
When did that happen?

Lee Gunter
Regence HMO Oregon




From: Scott McClellan <[log in to unmask]> on 03/10/99 11:43 AM

Please respond to Scott McClellan <[log in to unmask]>


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: Logging limit....(feedback opportunity!!!)




> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Schlosser, Robert (Contractor)

> The statement that each database has its own logging identifier
> is not correct. I have used multiple databases on a single logging
> identifier for related databases to keep all of the application
> data changes in the same logfiles. You can therefore have more
> than 128 databases open at one time.

I did not know that you could use the same logging id (and therefore
the same user logging process) for more than one database. Thanks
for this information. As you stated, this would mean that more than
128 databaseses could be open (with logging enabled) concurrently.

The limit for processes per logging id is a user logging limit, not
an Image Logging limit. Therefore I bleive that total number of opens
per logging id will still be limited to 1140 (eg: if you are logging
2 databases to the same logging id, I think you will be able to
have 570 process open each database - for write). I don't know how
it works if the same process opens both databases. I *think* each pin
requires another table entry - since they are the same pin they might
share an entry. It has been years since I looked at this code so I
really don't remember. Does anybody out there know?