You don't state the reason for your question, but if you've experienced a
problem with a :LOG logid, RESTART, chances are you've run into what I believe
is a bug which still exists in the user logging subsystem.  This occurs when a
:LOG ,STOP record is the last record written to the currently open log file
*AND* it fills the file at the same time.  The next restart of this process
fails because there's no room in the current log file in which to write the
restart record.

A better procedure is to include a ":CHANGELOG logid" (assuming you're logging
to disk *and* you've set up your logging process to "CHANGE" files) before you
stop the logging process.  This assures that your current logfile will have
capacity for the restart and subsequent transaction records.  We've set up our
LOG command scripts to automate this for each logging process.
----
Lee Gunter                    The Regence Group
Supervisor, TRG HP/MPE Systems     503.375.4498
----
Opinions expressed are solely mine.




From: JIM McINTOSH <[log in to unmask]> on 12/01/99 12:37 PM

Please respond to JIM McINTOSH <[log in to unmask]>


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  [HP3000-L] Restarting IMAGE database logging after a normal
      shutdown and              startup




Hello listers,

If one has successfully performed:

LOG logid,STOP

and then shutdown and started the machine for something like replacing a
tape drive,

should it not be sufficient to perform:

LOG logid,RESTART
?

Thank you in advance.

Jim McIntosh