HSM doesn't re-drive the migrate. It attempted to migrate to a SDSP that was still enabled. The migrate failed at which point that SDSP became dis-abled to HSM. If you have a product such as Mainstar's HSM Report Manager, you can track the SDSPs as they become disabled so that you know when a re-org is necessary. Alternatively just issue Listcat commands against the SDSP files and check HI-A-RBA-------359424000 HI-U-RBA-------129392640 When HI-U-RBA approaches HI-A-RBA, it might be time to drain the volume and issue the Freevol command or simply re-org the file. Personally I let the files fill up until most of the records have been deleted and then re-org them. Any files which fail migration are by definition small files which isn't going to impact my overall dasd space availability.
________________________________ Thanks David, I verified, and the reorg was run on March 18th at about 00:30. I noticed that there are several disks (15) which are in that pool. Is there a reason why other disks were not chosen by HSM? ---------------------------------------------------------------------- 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
