We are migrating a lot of data to new dasd subsystems. We are using various methods - one of them being DFDSS. But we are having problems with migrated datasets which have a GSPACE storage class
We do the following 1. init and enable new dasd volumes to storage group 2. disnew old volumes in storage group 3. DFDSS move the datasets. This works fine with most datasets However if a dataset is migrated and has a GSPACE storclas it seems to try and recall it to the volume it came from if this is in DISNEW and gets a problem. If the old volume no longer exists it seems to be Ok and will pick a new one. We are getting round this by enabling the offending volume, recalling and then move the gspace dataset and then disnew the volume again. Does anyone know of a better way. ---------------------------------------------------------------------- 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
