Todd, this is not a stupid suggestion at all. Many (most?) of these data sets contain back up copies of existing VSAM datasets, so restoring them without a rename would be a problem, unless I:
- restore them to my test system (no shared catalogs) - rerun DSS back up on test system, with output to DASD - Run DSS COPYDUMP on prod system to create final SMS managed backup GDG It would be like going all the way around the block to get next door, so I wouldn't want to do this for all the data sets getting converted from Tape to DASD, but for those 24 generation monthly / quarterly / yearly ones, it just might be worth the effort to free up the tapes. The other tapes will free up on their own soon enough. Thanks! Tom Chicklon ------------------------------------------------------------ This may be a stupid suggestion, but why not just restore the data to spare volume(s), and then recreate the dump on disk with the same dataset name as the current tape (rerun the dump)? Since the COPYDUMP command does not seem to be a good option, I'd just try to recreate the dump in another way if it was that important to move it. C. Todd Burrell Senior z/OS Systems Programmer ITSO (404) 498-3299 (404) 723-2017 (cell) ---------------------------------------------------------------------- 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
