@listserv.uark.edu
Subject: Re: Setup XLINK
XLINK makes it possible to protect multiple minidisks on a shared pack.
XLINK checks cylinder ranges.
You can test this
- on VMA, use LINK userid vdev 1 M
- on VMB try LINK userid vdev 1 M
and this should fail, CP should tell userid vdev not linked, R/W by
VMA
Note
Hello Listers,
I am looking into XLINK. The main goal is to be able to determine if a
minidiskextent on DASD is already in R/W use on a different VM. This way
we
could provide for an easy switch for linux guests from one VM to another.
We do not setup the full CSE here. SPOOL and DIRMAINT are
XLINK makes it possible to protect multiple minidisks on a shared
pack. XLINK checks cylinder ranges.
You can test this
- on VMA, use LINK userid vdev 1 M
- on VMB try LINK userid vdev 1 M
and this should fail, CP should tell userid vdev not linked, R/W by VMA
Note that there are no commands to
On Tue, Mar 17, 2009 at 12:32 PM, Kris Buelens kris.buel...@gmail.com wrote:
XLINK makes it possible to protect multiple minidisks on a shared
pack. Â XLINK checks cylinder ranges.
Incorrect Kris. XLINK only protects the starting cylinder. However, as
long as magic ensures identical directories,
If you use anything larger than a 3390-3 - I believe you'll need the first 9
cylinders (0-8) reserved for XLINK data. Not too bad if you're just doing
the z/VM volumes - some extent rearranging -- but it can be a major effort
if volumes with Linux data are included.
Scott
On Tue, Mar 17, 2009
Also: for a 3390-9 you can move the CSE area. When you define the
volume in SYSTEM CONFIG you can include a parameter that indicates the
starting cylinder of the CSE are - this means you can move it to the
end of a volume if you want to CSE protect a volume that already has
minidisks on it.
The
