Hi All,

   Thanks for providing lot of good suggestions on the SHUTDOWN command
   proposal. Also I thank Gavin for taking time to provide alternate or
   enhanced proposal and sharing his thoughts on how SHUTDOWN should be
   implemented.

   Let me first recap the original request, and share our thought process
   in coming up with our proposal and on the feedback we received.

   The original SIB enhancement request is ...
   ---------
   Description: Provide shutdown mechanism with a reboot option similar
                      to HP-UX.
   Benefit: Allows for proceduralization of automated shutdowns.
            Critical component of emergency shutdowns initiated by the UPS.
            Also, this item is more powerful when combined with SIB item #14
            (integrate MPE with UPS units); however, it has merit on its own.
   ---------

   As we understood there are primarily two features required - ability to
   RESTART a system with SHUTDOWN and ability to handle emergency shutdowns
   by UPS. Given this requirement, we went ahead in seeing how best we can
   meet these two requirements with minimal R&D effort. Hence, we came out
   with the original proposal -- which is essentially a leverage of existing
   CTRL-A SHUTDOWN feature and making it available as a CI command.

   Even ourselves we were not sure about who should have access to
   SHUTDOWN command; again, our intention is not to replace CTRL-A SHUTDOWN
   with this new CI command, eventhough we might eventually end-up that way.
   Hence, we were thinking of limiting new CI shutdown command only to SM
   or SM/OP etc.

   Based on the initial feedback received majority of them are
   concerned with allowing OP or SM or only to MANAGER.SYS login etc.
   We also learned that few application vendors/tools give/require OP
   capability to operate their tools etc. Hence, eventhough as per our policy
   we can provide this command to OP. Due the concerns raised, we have tried
   to limit further and most of the suggestions (afterthought - I should
   not have used the word -vote)  were towards giving access only to
   MANAGER.SYS.

   Hence, we thought probably we will limit to MANAGER.SYS and further
   asked for your feedback.

   I am sure you will understand our dilemma on how to take care of
   customers who were forced to give OP because of application tools
   (risk to customers system's reliability etc) or go head with MPE stated
   policy on such commands or be conservative and provide the access only
   to UPS and MANAGER.SYS.

   Thanks again for all the comments and suggestions. I would really
   appreciate if you could help us to decide the workable option for this
   command access (ASAP to meet our project goals :-).

thanks and regards

Shashi

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