Oh, and since the dataset is written to ML1, the space it occupies is available for allocation when it is recalled. You don't occupy the space for a second dataset while it is copying.
On Wed, Sep 25, 2013 at 11:33 AM, Mike Schwab <[email protected]> wrote: > When you Migrate by VOLUME, it does a recall of all datasets within a > few minutes. > When you migrate by DSN, it does not recall the dataset until requested. > > On Wed, Sep 25, 2013 at 8:44 AM, Jon Perryman <[email protected]> wrote: >> The drawback to HSM migrate is that the datasets are migrated until the next >> use. If the use of any of these datasets can't tolerate the recall delay, >> then you will need to ensure it get's recalled before that time. >> >> Jon Perryman. >> >> >> >>>________________________________ >>> From: Mike Schwab <[email protected]> >>> >>> >>>http://pic.dhe.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.arcf000/s6085b.htm >>>MIGRATE VOLUME(SG1001) >>>MIGRATE VOLUME(SG2003 MIGRATE(0)) >>>MIGRATE VOLUME(SG1002) DAYS(0) >>> >>>On Wed, Sep 25, 2013 at 7:30 AM, Jim McAlpine <[email protected]> wrote: >>>> Is that a DFHSM command, if so I'm not familiar with that, I've always used >>>> DFDSS. >>> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [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? -- 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] with the message: INFO IBM-MAIN
