On Thursday, 08/23/2007 at 09:28 EDT, David Boyes <[EMAIL PROTECTED]> wrote:
> In fact, does OPERATOR really need anything but C and G for normal > operations? B would be convenient, but thinking about this as a more > general lockdown and cleanup, it might be worth tightening things up a > bit now that we're not really doing apps on CMS any more. I would say that human operators (not sysprogs) will tend to want - VARY / ATTACH / DETACH - FORCE / XAUTOLOG - SET / QUERY / INDICATE - START / DRAIN - WNG / MSG - HALT - ENABLE / DISABLE - SIGNAL - SNAPDUMP - SHUTDOWN The other class A commands are really for sysprogs. (Do you really want the operator to issue ASSOCIATE EXIT, CPXLOAD, or MODIFY COMMAND?) DEFINE MDISK is controversial. I'd place it under ESM control, but I still need a provision for "in case of emergency break glass". I guess I'm paranoid that it will get into the wrong hands, but that it will be prevented from being placed in the *right* hands! "YOU HAVE REQUESTED DEFINE MDISK ACCESS. CONFIRMATION BY ANOTHER ADMINISTRATOR IS [NOT] REQUIRED. PRESS F5 TO CONFIRM. BY DOING SO YOU SWEAR (OR AFFIRM) THAT A STATE OF EMERGENCY EXISTS AND THAT DEITY-LIKE POWER IS NECESSARY TO CORRECT THE SITUATION. ALL COMMANDS FROM THIS POINT ON SHALL BE RECORDED FOR SUBSEQUENT AUDITING BY DATA SECURITY DRAGONS. THIS WARNING WILL NOT APPEAR AGAIN DURING THIS SESSION. ... "WELCOME AND THANK YOU FOR CHOOSING DEFINE MDISK TODAY. PLEASE DRIVE CAREFULLY." Alan Altmark z/VM Development IBM Endicott
