OK, I would like to add my $0.02 to this thread. <soapbox> You may want to consider the old adage of "be careful what you ask for, you may get it" may apply to this topic. Consider if you will, something happened to z/OS that was sever enough to cause a wait state and/or stand-alone dump to occur, what are the chances that the system can be safely restarted without some investigation into the matter. My personal opinion is that z/OS is fairly bullet-proof and if something has caused z/OS to throw its hands up in the air, maybe someone should look into it first before trying to re-IPL. There is a similar option in z/VM-land on the SHUTDOWN command to REIPL the system automatically once the SHUTDOWN processing has completed. I have used this REIPL option on the SHUTDOWN command several times when I wanted to make some configuration change(s) only to discover that I caused a problem for myself by overlooking one thing or another. The software did what I told it to, but it was not smart enough to recover from my error. I have lost spool files and named saved systems by doing this only because another copy of a z/VM system volume was discovered during the IPL and this system's IPL was not using the correct set of volumes. Like I said, this was my error and not z/VM's.
What if z/OS and JES2 decided to do a cold start on your auto re-IPL or found the wrong copy of a system volume, PARMLIB, etc.? </soapbox> HITACHI DATA SYSTEMS Raymond E. Noal Lab Manager, San Diego Facility Office: (858) 537 - 3268 Cell: (858) 248 - 1172 ---------------------------------------------------------------------- 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
