you'll get a more complete answer soon, but this looks strangely like the
seemingly berzerk startup routine we once had in place here.

the idea is that when OPERATOR.SYS first logs on, she executes the udc "op"
*because* it has option logon.  then, if her session# is low enough, we must
have just restarted the system (valid once upon a time, long ago and far
away), so we need to do this other system startup stuff, including bring up
the network, etc.  stop 152?  dunno, try help stop.

> 1. Regarding the file below: setcuser.operator.sys
> op
> option logon
> if hpjobnum < 3 then
> stop 152
> netstart
> stream jinetd.netsys
> run sallp016.expr.expl;lib=g
> endif
> deldate0.pub.sys
> ***
> deltc
> deldate.pub.sys
> ***
>
> netstart is in an UDC:
>
> NETSTART
> option nohelp
> netcontrol start;net=loop
> netcontrol start;net=lanns
> nscontrol start
> ***
>
> What means "option logon"?
> The file (setcuser.operator.sys) is used as set catalog and
> it executes
> automatically at logon
>
> 2.  At beginning, the job j1 is jinetd.net sys. Why logoff j1 instant?
>
> **********
> Posted from www.3kworld.com
>
> * 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 *