Lee writes:
> START RECOVERY is also required to properly recover TurboImage
> transaction log files.

Just as a start RECOVERY will look at the *disk* copy of the JMAT table for
jobs with the ;RESTART option, it will also look at the disk copy of the
tables that keep track of user logging processes and will cause a "system
crashed" record to be written to each logfile that was open at the time of
the failure.  I don't *think* that this will result in any more logged data
making it to disk than if you did a NORECOVERY, but I'm willing to put user
logging (i.e. Image logging) into a category that *does* depend at least to
some degree on the type of restart (on both MPE/V and MPE/XL|iX).  But for
normal (i.e. all other CM and NM file types, spoolfiles, databases, KSAM,
etc.) files, the recovery processes which MPE undertakes on a system restart
(specifically when a volume set is mounted that was not "closed" properly)
are the same regardless of the type of start that was done.

So if you're not using Image logging, and you don't use the !JOB;RESTART
feature, and you're on at least MPE/XL 2.1 (r whenever it was that NMS
showed up), and you haven't made configuration changes that you *don't* want
to take effect, then you might as well always do a START NORECOVERY after a
system crash.

And I'll be happy to listen to arguments to the contrary.

G.