When we copy databases to other accounts for "test" purposes, it is our
normal procedure to go into DBUTIL and turn logging off for the copy.
(Since we know that having logging turned on for the copy is
superfluous, and would just screw it up.)  Turning off logging for a
Database also leaves the LOGID in the root file as an "anachronism", and
is also ignored.

Here is part of a VESOFT job below that would disable logging everywhere
in an account:

REPEAT
  CHGROUP ![RGROUP.GROUP]
  REPEAT
    RUN DBUTIL.PUB.SYS;INPUT="DISABLE ![RFILE.FILE] FOR
LOGGING";INPUT="EXIT"
  FORFILES @(INTCODE=-400)
VEAUDIT FORGROUPS @.{hpaccount}

Tracy Johnson
Measurement Specialties, Inc. 

BT







NNNN


> -----Original Message-----
> From: HP-3000 Systems Discussion 
> [mailto:[log in to unmask]] On Behalf Of Gilles Schipper
> Sent: Tuesday, November 18, 2008 6:33 PM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] IMAGE [allbase/odbc] error
> 
> 
> 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.
> 
> 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?
> 
> --------------------------------------------------------------
> -----------------------------------
> Gilles Schipper
> GSA Inc.
> HP System Administration Specialists
> 300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
> Voice: 905.889.3000     Fax: 905.889.3001
> email:  [log in to unmask]  web: http://www.gsainc.com
> --------------------------------------------------------------

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