I was going to ask Mark how (and if) fencing works in a basic sysplex when Skip (very oblingingly) provided the answer that it doesn't. :-(
So, in Kens case, he will always get IXC102A. >A strong word of caution: >DO NOT automatically reply DOWN. Mark, does this apply to a basic sysplex, too? Or would Ken be safe having automation reply to it? Ken, from your couplexx, it appears that you do have an SFM CDS. You will need to run this job to see what was defined as a policy. //STEP1 EXEC PGM=IXCMIAPU //SYSPRINT DD SYSOUT=* //SYSIN DD * DATA TYPE(SFM) REPORT(YES) Then you need to read up on *what* is defined and what is defaulted, and check against the values I mentioned before and how they work together. EXSPAT is excessive spin parmlib member, decribed in Init&Tuna. My word of advise is to remove the parms INTERVAL, OPNOTIFY and CLEANUP from your couplexx and have them default to whatever IBM thinks it should be. Same goes if you have an EXSPATxx parmlib member defined and active. If this gives you the longer interval before TCPIP starts complaining, then all is fine. Otherwise you will need to 'tweak' the values for the above parms. 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
