Ups, forgot the SFM policy. (We have it active.) BUT: I have also seen IXC102A *even though* sfm was active. *That* was a bug.
The book says: 3. There are instances when this message will be issued and the appropriate action must be taken even though there is an SFM policy active in the sysplex. If SFM cannot successfully isolate the system image being removed, manual intervention will be required. This message will be issued and must be responded to. So I guess the question is if there is an SFM policy active. If so, there should not be any message, and it needs to get investigated why isolation via the CF (this is what SFM actually does) does not work. This may take an IBM ETR to figure out. (In my case it was a mismatch in code, and I think I got it solved by contacting someone in IBM development directly.) If there is no SFM policy, then one should be defined. Ours just contains this: DEFINE POLICY NAME(SFM01) REPLACE(YES) CONNFAIL(NO) SYSTEM NAME(*) WEIGHT(100) PROMPT Best regards, Barbara ---------------------------------------------------------------------- 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
