Connie Sellitto writes



To make a long story short, a job invoking QUERYNM had to be aborted, as it
was using up all system resources (no ASSIGN LOCKOPTION=OFF statement).  I
was unable to abort the job form the system console - no response after
several minutes.  Tried Ctrl-B and started the reboot (from disk) process.
Got through date/time question, ISL> START NORECOVERY etc... up to 'Leaving
- Mount all volumes' message.
Got message 'The current boot comand has been saved on the system master."
Then!
NMMON: CREATEPROCESS error 16 on NMFILE.PUB.SYS (NMCNERR 5)
NMLG FILE NUMBER 83 on.

And then nothing - the console has been sitting idle for 10+ minutes.  This
is most unusual.  I know the reboot takes awhile in the initial stages,
with the I200 state showing in the lower left of the screen. but I've never
had to wait this long at this point.

QUESTION:  Is the 'CREATEPROCESS error 16' crucial?
What could be causing delay?

I hate to have to go back to reboot from tape.... could someone please post
instructions for this, as it's been years since I've done that.
-------------------------------------------------------------
CREATEPROCESS error 16 reads as follows:
Process not created; hard load error occurred (for example, I?O error
reading formaldesig)

NMFILE is a system file that comes in with a boot tape.  Possibly it is
clobbered.  Maybe you could do an update from your latest sysgen tape and
bring it back in.

Mike Berkowitz
Guess? Inc.

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