On Tuesday, 11/25/2008 at 11:19 EST, Marcy Cortes <[EMAIL PROTECTED]> wrote: > >The SA Linux piece handles the error detection, communication with > SA390, and the CP HYPERSWAP command at the right times. > > Which still feels backwards... The guest controlling the hypervisor in > big serious matters like i/o ... :)
Fear not! SA Linux is actually the instigator. It detects the I/O failure, suspends I/O locally, signals SA390 to break and reverse the PPRC connections, waits for completion, then HYPERSWAPs the I/O locally and resumes I/O. (Simple to say, a mite bit harder to do.) In this case, think of z/OS as z/VM's errand boy. :-) He's a big boy, with chubby cheeks, to be sure, but slave to the whims of VM. Ahhhh..... "Oh, z/OS! z/OS! Another drink, if you please. Be sure to put an umbrella in it. A blue one. No no, not sky blue, but one of azure. You're such a dear. Now go on and play - I'll call again if I need you." Alan Altmark z/VM Development IBM Endicott
