Unless they are your system volumes, Step 1. Implement SMS (at least for the new volumes)
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Jon Brock > Sent: Tuesday, July 15, 2008 1:00 PM > To: [email protected] > Subject: Re: Moving 3390-3 to 3390-9 > > I had considered that, but there are tons of data sets on these volumes, > some of which rarely get reorged. > > The volumes aren't SMS-managed, so I can't use the pool method that > Lizette mentioned, either. > > Jon > > > > <snip> > I have another possibility that I have used when moving to new dasd. > Just > change the delete defines to either point to the new packs or to the new > > storage class for the mod 9's. Then, when the dataset is reorged, as > long > as it gets reorged on a daily, weekly, or montly or whatever basis, it > will > get moved. > </snip> > > <snip> > > If the M9 is in a pool, you could just copy the datasets to the new > volume > > with DFDSS. > </snip> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
