Lee Gunter wrote in message ...
>... unless your EDITOR.PUB.SYS file inhabits a non-LDEV1 device on $SYS,
>like ours does.  EDITOR is not considered a system file, so it's not
>captured on a CSLT.  I think that was a big mistake.  (Of course, I could
>rectify that for our systems, and I fully intend to do so ... Real Soon
>Now! :-)  We've been in just the situation you describe -- single-disk,
>single-user mode *without* an editor.
>


The file *everyone* should check for is PERFLOG.MPEXL.SYS. This file must be
available when the system boots up or you will get a system abort. The file
label for this file is not by default nailed to ldev 1 or $system_master. It
is possible for this to find its way to other disks (e.g. RESTORE) It is
also created by MPE but is not put on an SLT.

So, IF perflog is not on ldev 1 AND you are forced to boot a single disk
system for any reason you will be in a catch-22. Can't boot the system up to
move perflog to ldev 1 because the system aborts before you get there. Can't
boot single-disk because perflog isn't there. Can't update to put a new copy
out there because it does not exist on an SLT...

While this would seem a rare occurrence, it can happen and has happened. The
only supported way to fix it that I know of is to re-install.

I would strongly suggest everybody do the following:
:rename perflog.mpexl,perflogx.mpexl
:file perflog;dev=1
:fcopy from=perflogx;to=*perflog;new

Doug.

Doug Werth                                     Beechglen Development Inc.
[log in to unmask]                                       Cincinnati, Ohio


The opinions expressed do not necessarily represent the views or opinions
of Beechglen Development. They might, but not necessarily. They represent
solely the opinions of the author.