Oh. If you want to recall a dataset, and the ML volume is busy, use the last backup volume instead of taking away the ML volume from a migrate task.
On Wed, Sep 25, 2013 at 11:49 AM, Staller, Allan <[email protected]> wrote: > I would like to see similar option w/HRECOVER. Not for the parallelism > (already provided in z/OS 1.12), but to reduce the number of commands > required. > > i.e. RECOVER an entire storage group with one command. Rather than (in my > case) several hundred HRECOVER VOLUME(xxxxxx) commands per SG. > > <snip> > Hi, other customers with similar scenarios have requested multitasking > support for MIGRATE VOLUME and the addition of a MIGRATE STORAGEGROUP > command. I am currently 'Accepting' requirements for this type of > functionality. Assuming that we deliver this type of functionality in an > upcoming release, hopefully it will provide the functionality that you need > by switching from single-tasked data set level migrations to parallel-tasked > volume or storage group level migrations. > > Use Case: After a customer creates their DB2 image copies in a specific > storage group, they want to be able to issue a single MIGRATE STORAGEGROUP > command and have HSM migrate all of the images copies to tape, using highly > parallel tasking. (They want to do it via command so that they can control > the specific timeframe that it runs as opposed to during IM top of the hour, > which often conflicts with other processing). > </snip> > > ---------------------------------------------------------------------- > 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? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
