But all of the tripwires will be clearly documented, right, Alan? ;-)
I'm guessing that the existence of these tripwires are because CMS is
now so tightly integrated in with CP and services provided by other CMS
based virtual machines. I can imagine the hassles of trying to migrate a
CMS virtual machine that has all of it's accessed disks stored in the
SFS over to another processor complex.
I wonder if z/OS will trip over the same tripwires.....
DJ
On 12/08/2009 04:29 PM, Alan Altmark wrote:
On Tuesday, 12/08/2009 at 12:14 EST, Dave Jones<d...@vsoft-software.com>
wrote:
And it will only be for Linux guests, as well.....CMS-based guests will
not be able to be moved between systems.
You will be able to relocate any guest that doesn't hit any of the
tripwires. But as it works out, CMS is like a porcupine in a balloon
factory, tending to trip over and bump into many of the inhibitors.
But Linux's halo is tarnished, too! Linux guests that use IUCV terminal
server will not be able to be relocated while they have an IUCV connection
between them.
Alan Altmark
z/VM Development
IBM Endicott
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Dave Jones
V/Soft
www.vsoft-software.com
Houston, TX
281.578.7544
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
