On Tue, 6 Nov 2007 11:27:00 -0500, Jim Bohnsack <[EMAIL PROTECTED]> wrot e:
>You might want to put this change in SYSTEM CONFIG as well. What we use is: > >Modify Command Shutdown IBMclass A Privclasses Z > >Over the course of 30 years as a VM sysprog, every VM sysprog who I have >worked with has shutdown a VM system *ONCE.* Me too :-[ > >Jim 1. I have never accidentally shut down a VM system. But then, I don't hav e any userids with class A (or class D) privileges. It always makes me cringe when I see a userid wi th class ABCDEFG. Like walking around with a loaded gun in your pocket! I have a CLASSA EXEC that issues: SET PRIVCLAS * +A CP command SET PRIVCLAS * -A when I really need a class A command. 2. We have a mod to CP SHUTDOWN that requires the system name on the SHUT DOWN command. Too many times an operator has shut down the wrong system. 3. We have a VM:Oper macro SHUTSYS that we prefer operators use. It does a clean shutdown, after bring various other things down cleanly. Maybe with the new SIGNAL SHUTDOWN this is not so necessary? 4. I am one of those that prefer the command be the same everywhere. I kn ow SHUTDOWN is dangerous. I hate it when QUIT or END is dangerous. 5. The real problem is that you shouldn't be able to bring a system down with just a single command -- no matter how you spell that command. Since at least the 1984 Apple Human Interface Guidelines, it's been expec ted that you ask the user before you let him/her do something irretreivable. Come to think of it, isn't that the same with XEDIT QUIT and QQUIT (some time before 1980)? Why doesn't CP prompt the operarator: "Are you sure you want to bring this system down? Your job may be on the line. Think about it! Yes Are you really, really sure you want to bring this system down? Yes Enter your name and Social Security number: etc. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
