Brian,

You should replace your NETSTOP udc with following commands:

  NETSTOP
  RUN STMSHUT.DIAG.SYS
  NSCONTROL STOP
  NETCONTROL STOP

Reason for that, basically, is when you NETCONTROL STOP one specific
interface (LOOP or LAN), "common" network code may remain loaded, even if it
was last interface to be stopped.  However, when you say "NETCONTROL STOP"
only, it means "stop everything".

HTH
--
=========================================
Denis  (Remove "removeit." from email address)
=========================================
"Brian Donaldson" <[log in to unmask]> wrote in message
news:34SdnaXnD5xvCSqiRVn-hQ@fidnet.com...
> Listers:
>
> Thanks to all who responded and tried to give me help.
>
> Yes, I streamed the JCONFJOB.NET as well as doing a host of other things.
> The system was hanging with no visible system failure message on the
console.
> No colon prompt and no network. The box was frozen/hung.
>
> However, as I don't give up easily, the solution to the problem was :
>
> 1) RENAME X25SERVR.NET.SYS,X25SERV2.NET.SYS (this took away the need for
the
> OVERRIDE option on netcontrol/nscontrol commands)
>
> 2) Changed my netstart UDC to :
>
> NETSTART
> NETCONTROL START;NET=LOOP
> NETCONTROL START;NET=LAN
> NSCONTROL START
> RUN STMSTART.DIAG.SYS
>
> 3) Changed my netstop UDC to:
>
> NETSTOP
> RUN STMSHUT.DIAG.SYS
> NSCONTROL STOP
> NETCONTROL STOP;NET=LAN
> NETCONTROL STOP;NET=LOOP
>
> It is now early Sunday morning, my box has been up and running all night
and
> all is right with the world again. We are now running under 6.5 PP3 at
last.
>
> The problem of the system failure/hang/freeze has been resolved seemingly.
> Once again, thanks to all who wrote to me with assistance.
>
> Brian Donaldson.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

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