On Mon, 28 Apr 2008 09:20:37 -0500, Bill Neiman <[EMAIL PROTECTED]> wrote:
>On Mon, 28 Apr 2008 08:52:52 -0500, Mark Zelden ><[EMAIL PROTECTED]> wrote: > >>I want to make sure I have these 2 points correct... >> >>For a planned removal (V XCF,sysname,offline) in a parallel sysplex OR basic >>sysplex, you will not see IXC102A if you have an active and properly >configured >>SFM policy. > >Not quite. As I noted, isolation requires that you have a CF connected to >both the target system and some other system from which isolation can be >initiated. A basic sysplex does not meet this requirement, so in a planned >removal you will see IXC102A. > >> >>For an unplanned removal, you will see IXC102A regardless of any SFM >>policy in a basic sysplex but may not see it in a parallel sysplex depending >>on your SFM policy. > >Again, not quite. Even in a basic sysplex, if the SFM policy specifies >DEACTTIME or RESETTIME for the outgoing system, another system on the >same CPC can initiate the specified action. Either of those has the desired >effect of terminating I/O from the outgoing system, so IXC102A would not be >issued. > > Bill Neiman > XCF Development > Bill, Thanks for the clarification. So why doesn't (can't) SFM prevent IXC102A after VARY XCF,sysname,OFFLINE if there is an active system in the same sysplex on the same CPC? It it just a SMOP, or is there a technical reason. Thanks, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
