Ray, This is a topic that we could discuss for hours. :) In my experience, typically no. What happens at our place is that MIM notices that a system is not particpating and issues a message. The OPS are supposed to go see if it's down, and if so, respond properly to the message. If they don't, then things may get hairy with the offending system still holding locks, etc.
The whole area is called SFM (Sysplex Failure Management) and IBM has spent considerable effort on it recently. There were several good Share presentations that touched on the topic, including two from Mark Brooks: http://proceedings.share.org/client_files/Share_in_Orlando_2/Session_9704_handout_1799_0.pdf http://proceedings.share.org/client_files/Share_in_Orlando_2/Session_9729_handout_1740_0.pdf And in one of Cheryl Watson's Hot Flashes she stated, and I'm paraphrasing: "If you're not implementing SFM you are negligent'. The following (old but still relevant) redbook may help also: http://publibfp.dhe.ibm.com/epubs/pdf/e0s1p702.pdf As for QUIESCE, I'm not really sure. It's not a command I use. (Or have ever used??!) You could also try just VARY XCF,sysname,OFFLINE, but I don't think that would truly test out SFM. MA ---------------------------------------------------------------------- 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
