Well, I have a presentation that talks specifically about cloning VM (I'll
send it to you off list if you want it).
Basically, the answer to cloning VM depends on your environment. On the one
hand, if you have a shared DASD environment (like me), in addition to
copying the system volumes (SYSRES, SPOOL, PAGE + any USER volumes), you
would need to update the SYSTEM CONFIG file (on the Parm disk) and the VM
Directory (source + directory blocks) so that they point to different
volsers, as you would be using a different set of volsers, i.e. 520RES =>
NEWRES. On the other hand, if you have non-shared DASD volumes in each
LPAR, then you can just copy them to a new set of addresses with the same
volsers and bring it up in the "other" LPAR as there would not be any
duplicate volser issues. However, in either case, allowances would still
have to be made for TCP/IP access - at least the home IP address for the VM
system would need to be unique - possibly OSA addresses as well (depending
on how your hardware is defined in each LPAR) - this can be taken care of
from the VM console after the initial IPL.
As far as how to go about getting the changes made to the SYSTEM CONFIG &
VM Directory: before copying the volume that has the Parm disk on it
(SYSRES by default), you could simply make a copy of your current SYSTEM
CONFIG to, say, NEWSYS CONFIG, update the volsers, then when you IPL the
"copied" system the first time, specify the new filename, i.e. FN=NEWSYS
(on the SAPL screen before pressing PF10), but the VM directory requires a
bit more work. Again, before copying the volume that has the VM directory
source (again, SYSRES by default), you could make a copy of the directory
source, say, to NEWSYS DIRECT, update the volsers AND make sure that you
don't miss the DIRECTORY statement. Then, after the volumes are copied to a
new set of volsers, you would need to update the directory blocks with the
new directory (NEWSYS DIRECT). For example, assuming that the DIRECTORY
statement uses virtual address 123 (the default), you would attach the
address of the new SYSRES to your virtual machine as 123 (detach an
existing virtual 123 first, if needed), then run DIRECTXA against the new
directory, i.e. DIRECTXA NEWSYS DIRECT, which should write it out to the
directory blocks on the new SYSRES. Then you should be ready to IPL the
cloned system via the new SYSRES address and it will use all of the copied
volumes (by referencing the new volsers).
The scenario as described is intended to make as few changes as possible in
order to get a copy up and running, however, there are other, perhaps more
elegant approaches that could be used, for example, using a different
System Identifier, so that the same SYSTEM CONFIG could be used for both
systems and could allow a unique set of TCP/IP files to be associated with
each system as well. Also, I didn't address possible considerations(?) if
DIRMAINT is being used to maintain the VM directory.
"Santo, Anthony"
<anthony_sa...@me
dco.com> To
Sent by: The IBM [email protected]
z/VM Operating cc
System
<[email protected] Subject
ARK.EDU> Cloning VM systems
12/17/2008 04:17
PM
Please respond to
The IBM z/VM
Operating System
<[email protected]
ARK.EDU>
I would like to clone a VM system in order to build a new VM lpar;
Is there a documented process to perform this function?
Also are there any issues copying(using FDR) a 3390-3 dasd volume to a mod9
or mod27(other than wasting a lot of space).
Thanks…..Tony.
This e-mail message and any attachments contain confidential information
from Medco. If you are not the intended recipient, you are hereby notified
that disclosure, printing, copying, distribution, or the taking of any
action in reliance on the contents of this electronic information is
strictly prohibited. If you have received this e-mail message in error,
please immediately notify the sender by reply message and then delete the
electronic message and any attachments.
-----------------------------------------
This E-mail and its attachments (if any) are intended solely for
the use of the addressee(s) and may contain sensitive but
unclassified information. If you are not the intended recipient,
you are hereby notified that any disclosure, copying, distribution,
or use of the information contained herein (including any reliance
thereon) is strictly prohibited. If you have received this E-mail
in error, please notify the sender immediately and destroy the
E-mail and any attachments.
