No argument there. Jeff's post seemed to be pretty xlink-specific. Regards, Richard Schuh
> -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] > Behalf Of Rob van der Heij > Sent: Thursday, September 07, 2006 10:03 AM > To: [email protected] > Subject: Re: VM directory entry for shared DASD > > > On 9/7/06, Schuh, Richard <[EMAIL PROTECTED]> wrote: > > > I am not even sure that XLINK ought to be in the equation. > Requiring it restricts the functionality to CSE environments. > > XLINK is just the part that extends the LINK semantics over multiple > systems with shared DASD. It does not require additional communication > channels like ISFC or sharing of spool volumes. Obviously if you're > sharing volumes on mini disk level, you'd want something to ensure the > CP directory on all participating systems is the same (or otherwise > matches). > > Rob >
