Daniel, In the past, I have successfully run DFDSS Defrags on ML1 volumes, making sure that there wasn't any heavy ML1 migration activity going on at the same time. I needed to do so, in order to have contiguous space available for larger dataset migrations which otherwise would not migrate (at that time, I was chronically short on disk space everywhere and no new disks in sight).
IIRC, there may be some caveats regarding defrags, if the ML1 volume has an SDSP dataset on it. I'm not sure, where I heard about that ... either here on the List or in IBM manuals, but you might want to follow up on that if you use SDSP. (IMHO, discontinue SDSP. It ain't worth the hassle, from everything that I have heard.) Upgrade your FDR product, also check with the vendor if there are any known issues. But fix your VVDS issues first! Until you can get FDR upgraded, and if you must make space available on ML1 volumes (and have plenty of time), you can run the following DFHSM command against the most fragmented ML1 volume: HSEND FREEVOL MVOL(ml1vol) T(ML1) A(0) This will make DFHSM move all datasets on MVOL(ml1vol) to other ML1 volumes, one dataset at a time. Takes time, but gets the job done. HTH Regards, Ulrich Krueger -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Daniel McLaughlin Sent: Tuesday, May 29, 2007 9:02 AM To: [email protected] Subject: Compaktor and ML1 We upgraded to ZOS 1.7 this weekend and had an issue with Compaktor. We started getting U888 abends and found out our FDR was backlevel. The real question is: Is there a need to run Compaktor on ML1 volumes? It seemed to have scrambled some HSM VVDS entries....TIA. ---------------------------------------------------------------------- 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
