My personal opinion on the new SHUTDOWN command is:

1.  Make it ALLOWable (as I will probably want to include this
    in a JOB that is secured).
2.  If the command is issued from a session, prompt the user
    for confirmation (I would equally welcome this in batch
    mode too if an optional ";NOW" parameter could be used to
    override the prompting).
3.  Do not have the command read/use a fixed script file for
    optional shutdown commands.  Don't get me wrong, I want
    that ability, but I'd rather have complete control over
    this aspect of the shutdown and only after I know that
    I'm in a position to shut down the OS would I have the
    command file/job issue the new SHUTDOWN command. If and
    when we tie this in with the UPS monitor, I would want
    the script issued by a powerfail to include this new
    command, but what I do to shutdown the system at that
    point may be quite different than what I would do under
    "normal" situations.
4.  Include a DUMP option to perform a memory dump (although
    I can't think of a situation off hand where I would be
    "shutting" down the system and then wanting to get a memory
    dump.  If it doesn't take too much additional time to
    implement then I guess it might come in handy at some point).

Thanks for asking for our opinions.

Michael L Gueterman
Easy Does It Technologies LLC
http://www.editcorp.com
voice: 888.858.EDIT or 573.368.5478
fax:   573.368.5479
--


Jeff Vance wrote:

<snip>
I hope not.  One way we try to improve MPE is by soliciting input
from this list, as well as our support folks, ISVs and other partners.
Just so you know, providing this type of feature (a non-control-A way
to shutdown and optionally restart the box) was voted #5 in the recent
Interex Systems Improvement Ballot (SIB) polling.  See:
  http://www.interex.org/advocacy/survey/mpesib01results.html

<snip>

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