We have SHUTDOWN command in a privilege class of its own and only one ops userid has that class. That user has a SHUTDOWN EXEC on its A disk. Not to prevent the shutdown but to actually do it. It first checks that it's being run from that particular user and then asks a are-you-shure-type question. That pretty much eliminates the possibility of an accidental shutdown of the first level. I mean, you can still add that shutdown-only privilege class to your user and and then have an "oops!" moment, but then it's not an _accident_. It's not a death wish either. It's an intention to kill.
- Re: MAINTENANCE Tom Duerbusch
- Re: MAINTENANCE Schuh, Richard
- Re: MAINTENANCE Thomas Kern
- Re: MAINTENANCE Thomas Kern
- Re: MAINTENANCE Brian Nielsen
- Re: MAINTENANCE George Haddad
- Re: MAINTENANCE Jon Brock
- Re: MAINTENANCE Alan Altmark
- Re: MAINTENANCE Adam Thornton
- Re: MAINTENANCE Jim Bohnsack
- Re: MAINTENANCE Ivica Brodaric
- Re: MAINTENANCE Kris Buelens
- Re: MAINTENANCE pfa
- Re: MAINTENANCE Schuh, Richard
- Re: MAINTENANCE Alan Altmark
- Re: MAINTENANCE David Boyes
- Re: MAINTENANCE Colin Allinson
- Ops privs (was Re: MAINTENANCE) George Haddad
- Re: Ops privs (was Re: MAINTENANCE) David Boyes
- Re: MAINTENANCE Jeff Gribbin, EDS
- Re: MAINTENANCE Kris Buelens