Even HALT seems to be going the way of the Dodo bird. I can't remember the last time it was used effectively here. We tend to not have much tape and no printer (we let MVS do what it is good at :-}) activity.
The only START/DRAIN activity our operators need is SMSG RSCS ... . There is something to be said for not having UR equipment on your system. I would not want to put the starting and draining of disks in the operator's hands, so I would separate the UR and DASD forms in a slightly different manner, I would put DASD in a sysprog class, other than B, that is separate from the operator commands. Unless things have changed, the MAINT machine is A-G out of the box. That and the default passwords are the first things I change on a system. That reminds me of a story. When I left Amdahl to go to work for Piedmont Airlines in 1984, I changed the password of the IBMCE userid to AMDAHL on our first VM system. There was one IBM SE assigned to the account who absolutely refused to log on because of the password. All of the other IBM folks thought it was funny, so they would not change it for him. Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Thursday, August 23, 2007 7:14 AM To: [email protected] Subject: Re: MAINTENANCE 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
