BTW, Scott, thanks for the pointer. Looked into FDRDSF - dump/restore only (two-step). FDRCOPY is for disk-to-disk (still TYPE=DSF), and can select tracks, but CPYVOLID isn't an option in this case, so I'd have to then clip the destination volume. DSS COPY TRACKS with NOCOPYVOLID just seems easier. Too bad - otherwise we could kill two birds with one copy step.
On Mon, 22 Nov 2010 16:02:40, Mark Zelden <[email protected]> wrote: >We use 2 3390-9 for the IBM sysres and the zFS files (formerly HFS) are on >their own volume. Full volume copy is done for volume #1, but the zFS >dsns are logically copied to facilitate rename to match the sysres as >part of the dsn. I used to use indirect cataloging with HFS and no sysres >qualifier in the DSN until a 2nd volume was needed. Ours are similarly laid out, just deployed differently. We entertained indirect cataloging, but that made extra work for any post-copy SMP/E work. We put the &SYSR1 value in the HFS name, too. I'm still grappling with the whole HFS vs. zFS debate, as the long-held IBM recommnedations of "no VSAM on the SYSRES" and "almost no VSAM in the Master Catalog" are so ingrained. Guess I'm "old school", and I just don't see the need for these R/O FS. If you're interested in the SADump/HMC discussion, we can continue offline, or at least start a new thread. We've already drifted beyond the buoys. Regards, Art Gutowski Ford Motor Company ---------------------------------------------------------------------- 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
