Hi Mark Thanks for the reply. These are newly initialised empty volumes. We do the logical copy because we up-sequence the volume id, and build a new catalog (with the volume id in the name) as we go. Doing the large PDSEs first is a good idea though in terms of getting around the problem, although I still don't understand why 'spare' space is needed.
Best regards, David Tidy Tel:(31)115-67-1745 IS Technical Management/SAP-Mf Fax:(31)115-67-1762 Dow Benelux B.V. Mailto:[email protected] > Is the new / target sysres volume empty when you start, or is there an existing SYS1.SCUNTBL data set? Check out doc apar OW42335. Perhaps init the tgt volume first, copy the PDSE data set(s) first, then the rest in a second step excluding the PDSEs. I do a physical copy for a clone, not logical... so I would never have that problem. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[email protected] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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 ---------------------------------------------------------------------- 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
