The sysprog that established the need for a shutdown is responsible. The process is a set of four started tasks that issue appropriate commands in the right sequence. There are four because there are three points where a wait and approval as to when to proceed is reasonable.
There is only one task that issues -all- of the startup commands to include both production and test onlines. There is the odd prompt we have not bothered to fix. The scheduler handles all of the batch jobs. Operators are not involved in the IPL sequence. Since it is rare, there is little opportunity to learn and practice. And even fewer opportunities to screw up :-) -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ted MacNEIL Sent: Tuesday, July 28, 2009 12:27 PM To: [email protected] Subject: Re: Operator Validation before Executing Command >Part of our solution is that >a) operators never shut down an LPAR, and Who does it, then? At the risk of being facetious, who starts and stops jobs? Where do you draw the line? >b) LPARs are never routinely shut down. That is a good practice. - Too busy driving to stop for gas! NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
