Stan Sieler wrote:
>
> Re:
> > I think that a "SYSSTOP" script capability is an excellent idea.

> Actually, it's fairly hard to do correctly in all circumstances.  [snip]

I concur, and agree it would likely execute within the limitations of
the sysstart file (only so much it can do).  But especially for
shutdown, you want the relative power of a command file, perhaps enabled
to execute as MANAGER.SYS (which is what you can accomplish with a
jobstream, you can allow an operator or other person to invoke something
as manager.sys).  Perhaps what we need now is setuid command files :-)

Actually, something along the lines of a unix 'init' - where you define
various resources and have scripts executed in a particular sequence for
startup and shutdown.  But that's so much more complicated than a simple
command file.

We have a shutdown script, and a startup script that does non-SYSSTART
things.  We have operator.sys with a user-level UDC with a 'startup'
UDC.
In SYSSTART, we do a STARTSESS on the console for operator.sys with an
info string such that it executes the 'startup' UDC.

Jeff Kell <[log in to unmask]>