I define the following in SYSTEM CONFIG: /* Class S allows OPERATOR (and only OPERATOR) to issue SHUTDOWN */ MODIFY Cmd SHUTDOWN PRIVclass S DISABLE Cmd SHUTDOWN
When OPERATOR wants to shut down the system, they must first issue CP
ENABLE COMMAND SHUTDOWN, then issue SHUTDOWN.
Your gun, your bullet, your foot. But first you have to set the safety off.
;-)
Mark Wheeler, 3M Company
Alan Altmark
<[EMAIL PROTECTED]
ibm.com> To
Sent by: The IBM [email protected]
z/VM Operating cc
System
<[EMAIL PROTECTED] Subject
ARK.EDU> Re: Changing privclass of SHUTDOWN
11/06/2007 03:30
PM
Please respond to
The IBM z/VM
Operating System
<[EMAIL PROTECTED]
ARK.EDU>
On Tuesday, 11/06/2007 at 01:29 EST, "Schuh, Richard" <[EMAIL PROTECTED]>
wrote:
> I wholeheartedly agree about using SHUTDOWN for other than CP being a
> poor choice. Unfortunately, that has been the case for so long that it
> will be difficult to change it now.
And then there was the crowd who wanted the same command on all subsystems
so as to make it simpler. "Why does IBM invent a new command when we
already have a perfectly good 'shutdown'?"
And, no, nothing is going to change at this point.
Alan Altmark
z/VM Development
IBM Endicott
