How about adding a VSAM keyword that after reading the VTOC, looks up the VSAM CLUSTER and migrates the entire VSAM SPHERE too? Yes, it is slower, but doing each dataset is even slower.
Any way of doing something with 0 track or invalid datasets? I.E, reallocating them on another volume then deleting the old dataset? I think the ongoing example is a MANAGEMENT CLASS instead of a whole storage group. Of course, the STORAGEGROUP option would be great if limited to DISABLED storage groups or DISABLED volumes within that group, skipping any volume or storage group that is ENABLED. On Wed, Sep 25, 2013 at 10:33 AM, Glenn Wilcock <wilc...@us.ibm.com> wrote: > 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). > > Glenn Wilcock - DFSMShsm Architect > -- 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
