>===== "drain" means the operator begins to enter a series of commands at the operator console to stop/cancel the various jobs and stc-s that are running, culminating in the commands "z net,cancel" "$pjes2" and "z eod" >;; yes, "reset clear" is a possibility, but normally you don't have to do it 3 >or 4 times.
>"what do you see .... " ==== nothing on the operator console; after you enter your final "z eod" the stuff *already* on the operator console stays there until it blanks itself out (the screen does) when the series of messages beginning w/ IEA371I begin to arrive ;; when those messages DO NOT arrive after 5 minutes, we know it's hung up and then we go do the "reset/clear" >no, we do not get the ipl successful message at the HMC; in any case, the hardware console never changes color ; it's the (proprietary) IBM HMCz9B Hardware Management Console Workplace v2.10.0; we got one automatically w/ each of our z9 mainframes. it's a GUI-type thing: a "graphic user interface" All of the above strongly hints that the shutdown procedure is missing the v xcf,sysname,offline. This should *always* (yes, on a monoplex, too!) be the last command done in any shutdown. What it does is two-fold: a) it generates a wait state 0A2 saying that operator requested shutdown. At this point the wait state message appears *either* on the console in red or on the HMC, in which case the 'software message' icon will start blinking. b) the 'hardware message' icon starts blinking (because a wait state was loaded). Colour change on the HMC depends on what you set up for 'acceptable states', the blinking icons don't. While the v xcf,offline has nothing to do with a wait state after re-IPL (in which case the 'hardware message' icon should have been blinking), I doubt that an SQA shortage during IPL can be overcome by retrying the activate several times. Unless you have very faulty hardware that sometimes generates messages and sometimes doesn't. But *those* messages are visible on an operator console, I'm just not sure if that was on the NIP console or not. In my experience, SQA shortage during IPL is caused by a changed amount of UCBs (or faulty hardware generating IO messages), and the number of UCBs is determined by the IODF, and that will not change by several IPL attempts. Regards, Barbara Nitz ---------------------------------------------------------------------- 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
