Knut, looking at the messages you provided, why did you expect IXC256A? Were there problems with the sysplex CDS? Judging from the descriptor code (as I don't know which module would issue this message, and it is probably OCO anyway) this was a branch-entered WTO that is only shown 10 seconds on an MCS console before 'normal' message traffic takes over again. At that point it should be seen in the hardcopy log, though, provided you can get to it.
IXC427A was introduced a few years back when a customer had a definitely running system producing XCF traffic but there was a hardware problem accessing the sysplex CDS device (I believe some sort of ESCON director failure). So that system was partitioned out even though it shouldn't have. As a safeguard, SFM will only consider a system 'dead' when it is system status update missing *and* not having XCF traffic anymore. I believe that this applies to your case, XCF traffic but no status update. When reply 466 got DOM'd, apparently it had stopped its XCF traffic (entered a wait state itself?), so now SFM would have attempted to failure isolate the system. Bill would know why SFM cannot do it (the case the book eludes to, but does not elaborate on). So unless there is a way to automate (as in system automation/message trap) ixc102A (not recommended because of the possibly missing system reset), the operator will have to reply manually (after system-resetting). SA/390 has a part called proc/ops that would allow you to automate the system reset, I believe. What I don't know is how that would be done and if it could be done when failure isolation from SFM fails. Presumably they use the same interface. >Any ideas? Anything you have done in this area to help speed resolution >of multi-system outages? Is an outage this wide something that SFM >should be able to handle? Our SFM policy has one statement in it: DEFINE POLICY NAME(SFM01) REPLACE(YES) CONNFAIL(NO) SYSTEM NAME(*) WEIGHT(100) PROMPT We don't even allow automatic removal. And all systems are equal with respect to weight. I think, to preserve data integrity, SFM has done what it could and (without further logs - you didn't take an sadump, did you?) cannot do more. Regards, Barbara -- "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail ---------------------------------------------------------------------- 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
