----- Original Message ---- From: Gilles Schipper 

At 04:35 PM 08-11-18, Tom Emerson wrote:
>just as I was about to post this, I see above here that the LOGID is 
>invalid -- could that be a contributing factor?

It shouldn't be, since logging is disabled.

I've seen normally operating TurboIMAGE databases with invalid log id's.

In such cases, you would NOT be able to start logging without first 
correcting the invalid logid problem - but can operate normally 
without logging.

===========================

OK, good to know -- in this case, the database is "five-nines" read only ;)

it is (or will be) an archive copy of the production environment used for reference (looking up old orders) as the application is sunsetted.  there are only two things that I can think of that would generate a "write" to the database:  logging in we track the last access/number of attempts/password age and update accordingly, and when reports are generated we track the file number of the on-disk version of the report (for reprints)  Both of these functions can be eliminated if need be...

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