On Fri, 12 Aug 2005 18:26:38 -0500, Giovanni Cerquone <[EMAIL PROTECTED]> wrote:
>This means the end of the Sysplex Timers but does not mean the removal of >the restriction in the distance between the CPC's, although now it will be >increased to 100 KM. > >What are the shops doing know when this limit is reached?. Are they >trapped in this restriction?. > >How we can keep a Parallel Sysplex separated by distances greater to 100 >KM (to use the new limit) without implementing GDPS?. AFAIK, GDPS >automates the take over but you still will experiment outages. I am a bit puzzled but this sysplex thing . To start : with IBM mentioned to us that you do not need to have the 2 sysplex timer on each site .. you can increase a bit the distance by having your timers in "in between locations " like this cpux---timer1----timer2 -----cpuy This is increasing the distance ( limited because of the protocole) BUT there is an enormous BUT Who is able to make Data Sharing at long distance ? As far as i understand DB2 Data Sharing is not working at say 20 km ( well it is somehow but syncronous request are converted to async in the CF ) What i mean is that we have to stop data sharing a looonnnngggg time before we reach the sysplex timers or the PPRC limitations . Can someone correct me if i am wrong ? and give me the "production distance" they are able to use ? Bruno Bruno(dot)sugliani(at)groupemornay(dot)asso(dot)fr ---------------------------------------------------------------------- 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
