On Tuesday, 01/12/2010 at 09:43 EST, Ray Waters <ray.wat...@opensolutions.com> wrote:
> One thing that may of caused your VSE to be forced is your setting of RUN. If > it is on, it should keep your VSE from being forced. You can do that, but it doesn't make the problem go away. SET RUN ON, among other things, simply prevents CP from putting up a CP READ under certain conditions. It is the interaction with a "broken" console that triggers the Countdown to Oblivion. IMO, it is better to turn off the disconnect timeout and instead use system automation software like IBM Operations Manager for z/VM to monitor your system for VM READs (console request or CMS abend) or CP READs (e.g. disabled wait) by your fave virtual machines. It can then react in any way you wish: restarting them, answering them, forcing them, SEND CP baduser LOGOFF (rather than FORCE), SEND CP baduser MSG OBIWAN HELP ME, YOU'RE MY ONLY HOPE!, whatever. The *VMEVENT system service that Operations Manager watches tells you when the Countdown to Oblivion begins. You can then catch the event and forward it to some external service that starts a big red LED-style wall clock. 15:00, 14:59, 14:58, bwahahahahaaaa!!, 14:55, 14:54, the End of the World is Nigh!, you will all 14:50 adakjf aoty* (ouch! ouch!) in searing (ow! stop hitting me!) GET AWAY FROM THE KEYBOARD! Sorry about that - there was a slight disturbance in my office. It has been resolved and control returned to civilian authorities. (He's a smart one. You can see him testing the fences - working things out.) Alan Altmark & Co. z/VM Development IBM Endicott
