Douglas Becker wrote:
>
> Remember that this was during the days of MPE V on the now "classic"
> machines.
>
> I presume there was no parm=-1 or enforcelogonudcs and there certainly no
> alternate group from which to boot.
>
> And yes, I did know him personally--most of the time a brilliant system
> administrator, so things like this could happen to almost anyone [and
> thanks to his example, it never happened to me (you can just forget about
> the time I took a system dump over all the payroll checks while they were
> printing!)].

Many years ago, this did happen to me on an MPE/V system. We were doing
a Reload anyway, only about 1/2 hour into it so we simply restarted the
Reload. But I wondered how you get out of this nasty situation. What I
finally came up with, and never had to use, was a way to disable UDCs
while the system was down. This trick may actually be of use to any of
you who still have Classic systems.

Use the DUS tape (you did make one for your current OS release didn't
you?), Load and start SADUTIL. For the file COMMAND.PUB.SYS, turn on the
Store bit (this prevents the file from being opened when you logon) and
increment the Coldload-ID (this prevents the Store bit from being
cleared on the first FOPEN after the the system is restarted). Boot the
system normally. When you logon, you will get some error msg about
COMMAND.PUB.SYS and there won't be any UDCs. You are now on the box
without a Reload.

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