As part of our Sarbanes-Oxley compliance effort, I will be turning on
IMAGE logging for a number of databases (over 60 of them).
As you might guess, this means I have to increase the parameters for
logging in SYSGEN. 

My question is:
Are there any things I should "worry about" when upping the number of
logging processes and the number of users per logging process?
My understanding is:
-  I need to define one "user logging process" for each Image Database
that is enabled for logging
-  I need to set the "# of users per logging process" equal to (or
grater than) the maximum number of concurrent DBOPENs for a database.

For example, if I turn on logging for 65 Image databases, I need to set
"# of user logging processes" greater than 65.
If 64 of those databases have 5-10 concurrent DBOPENs, and one of them
has 850 concurrent DBOPENs (a very busy DB indeed), then I
must set the "# of users per logging process" equal to at least 850.

Do I have this right?  Is there a significant resource penalty for
setting these variables overly large?
I will NOT be using the Image Logfiles for recovery, they are only going
to be used to provide an audit trail for changes made to certain fields
in 
the databases.  But I am aware that I must keep an eye of discspace,
because it can be consumed very quickly.

*****************************
Terry W. Simpkins
Director ISIT
Measurement Specialties
757-766-4278
[log in to unmask]
*****************************

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