For who have DIRMAINT enabled and properly configured (file EXTENT CONTROL, at least), the steps 1-5, 7 and 9 can be substituted by a unique command: DIRM CMD (ChangeMDisk). The step 6 can be started as a batch of commands, using several CMD commands; see DIRM BATCH. Full packs can be managed the same way, if defined as MDISK ... DEVNO, Doesn't work for DEDICATEd dasds. And the command DIRM CLONED can be used to duplicate MDISK: alloc, define and populate (even if fullpacks with DEVNO). Commands very useful. Regards, Clovis.
David Boyes
<dbo...@sinenomin
e.net> To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<linux-...@vm.mar
IST.EDU> Subject
Re: Z/Linux CKD DASD migration from
one DASD Subsystem to another
21/01/2009 16:42
Please respond to
Linux on 390 Port
<linux-...@vm.mar
IST.EDU>
On 1/21/09 12:02 PM, "tony...@bellsouth.net" <tony...@bellsouth.net> wrote:
> Hi all,
> I would like to know what ways you have used to migrate z/Linux CKD DASD
> volumes from one DASD subsystem to another? Thanks.
If you used minidisks (the right way, IMHO) then you:
1) Allocate new minidisks on the new array using a knowable pattern, eg if
you have a 150 on the existing guest, allocate a new minidisk at F150 on
the
userid. Do this for all the minidisks on that userid.
2) Shut the guest down. You need to do this to get a good copy.
3) From an appropriately privileged ID (MAINT, etc):
LINK guest 150 150 RR (you don't need/want write access to this
volume)
LINK guest F150 F150 MR (you're going to overwrite this one, so write)
4) DDR the contents of one to the other:
DDR
SYSPRINT CONS
INPUT 150 3390 SCRTCH
OUTPUT F150 3390 SCRTCH
COPY ALL
<blank line>
5) DETACH 150
DETACH F150
6) Repeat #3 and #4 for all the other minidisks for that userid.
7) Update the CP directory and swap the MDISK definitions for the 150 and
F150 MDISKs (make the old one F150, and the new one 150). Repeat for all
minidisks on that userid. Write the CP directory either by hand or using
your directory manager. If you want, you can just comment the old disks out
in the directory entry in case you need to switch back for some reason.
8) IPL the guest as normal. That id is now running on the new disks.
9) Deallocate the Fxxx disks. If you commented them out in step 8, they are
now free disk space until you overwrite them or reallocate the space.
10) Repeat for all guests.
If you used dedicated volumes, now you pay for it. There is a procedure on
linuxvm.org to do this -- you get to do it the hard way.
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
<<inline: graycol.gif>>
<<inline: pic08271.gif>>
<<inline: ecblank.gif>>
