Mike, with the sms migrate command does hsm have to active? I interpret that to be true from reading the hsm admin guide. Does that sound correct? Tks Matt
Migrating an SMS-managed volume You can cause data sets to migrate from an SMS-managed volume by using the MIGRATE command. The MIGRATE VOLUME command can override some management class attributes that control when an SMS-managed data set is eligible to migrate, depending on the form of the command. The MIGRATE VOLUME command migrates data sets for which the management class COMMAND OR AUTO MIGRATE attribute has the value of BOTH only. When you issue a MIGRATE VOLUME command for an SMS-managed volume: migration is from level 0 volumes to ML1 or ML2 volumes only. the volume is considered to be DFSMShsm-managed. DFSMShsm maintains control records for the volume until a DELVOL command is issued for that volume. a list of the management class definitions required for processing the SMS-managed data sets on the volume is obtained. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mike Schwab Sent: Tuesday, February 16, 2016 3:19 PM To: [email protected] Subject: Re: Using IBM z/OS TDMF Product to Migrate 3390-9 to 3390-27's Yes, you can use TDMF / FDRPAS / etc, to move a volume to the same size or larger. After the move is complete TDMF or you run ICKDSF to pick up the new size. The VTOC and VTOCIX are not extended. You should select the volumes with the hardest to move datasets. If you need to increase the VTOC / VTOCIX, you can do that right after you get the new size. Or you can create new volumes and migrate the datasets from all old volumes. Remaining volumes will need to have the datasets moved to volumes on your new hardware. https://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieag100/v1stor.htm VARY SMS,VOLUME(volser,sysx),QUIESCE or (V SMS,VOLUME(volser,sysx),Q) will disable allocations to old volumes, unless it does not have enough space on non-Quiesce volumes. https://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.arcf000/migratesmsvolume.htm?lang=en After setting volser to Q, command MIGRATE VOLUME(volser) DAYS(0) will migrate datasets to other volumes in the storage group. Datasets in use or not eligible to migrate will be left behind. https://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.arcf000/s6068.htm?lang=en VSAM datasets with 2+ AIXs must be migrated with a command to the base cluster name. LDMF (Part of TDMF) can help move up datasets left on old volumes. On Tue, Feb 16, 2016 at 1:53 PM, Jasi Grewal <[email protected]<mailto:[email protected]>> wrote: > Greetings, I would like to know, if we can use IBM z/OS TDMF to migrate z/VM > and zLinux DASD to newer model 3390-27's from 3390-09. > The other problem is that we don't have that many targets as Source vols so > every MDISK would have to be migrated to consume DASD Space and does TDMF > supports the feature of copying MDISK's from Source to Targets or does it > only supports Full Volumes migration. > > Or do we use copyddr tool to copy mdisks from source to targets from z/VM > System. > Any experiences or recommendations would be greatly appreciated. > > Thanks in advance, > Regards, > Jasi Grewal. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected]<mailto:[email protected]> with the > message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
