> For the second time we have had an operator issue a vary command from > the master console that spanned nearly all our hardware devices, of > course to all systems in the sysplex, the command "v f00-f002,offline" > resulted in us having to ipl all the systems to recover. > > Has anyone perhaps had a similar problem and what solution was used to > stop is happening again ?, also anyone got any ideas on how to ensure it > does not happen again. > > Our current thinking is around an assembler exit to trap all vary > commands, but trying to avoid that solution . We are a Top Secret shop.
After we went 4 char device addresses we had this happen twice in a few weeks - different operator, different shift. I knocked up a cmdx exit to restrict all vary ranges to 32 (consecutive) devices. The DASD management folks whinge and moan whenever they are moving a lot of devices, but if I'm feeling particularly magnanimous I'll deactivate the exit on the sandpit for them, and they do their work there. Hasn't caused any major ructions, and has saved a couple of incidents I know of. Shane ... (this customer has no automation software deployed) ---------------------------------------------------------------------- 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
