Depending on your file system activity something like the following might be acceptable:
/usr/sbin/mount -t HFS -f NEW.HFS /yyy pax -rwvCDM -p eW /xxx /yyy /usr/sbin/unmount -o normal -f NEW.HFS <== z/OS 1.11 /usr/sbin/unmount -o normal /yyy /usr/sbin/unmount -o normal -f OLD.HFS <== z/OS 1.11 /usr/sbin/unmount -o normal /xxx /usr/sbin/mount -t HFS -f NEW.HFS /xxx Regards, Kevin -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Linda Mooney Sent: Wednesday, February 09, 2011 3:40 PM To: [email protected] Subject: Re: HFS file questions Hi Dick, Nobody here, me included, has ever used copytree. None of us know much about USS at all, although I am determined to learn - if it kills me! I need to end up with the same structure and directory names that I have now, just with more space available. Can copytree do that? How would I mount the new and old HFS files for the copytree process? Thanks, Linda ----- Original Message ----- From: "Dick Bond (DIS)" <[email protected]> To: [email protected] Sent: Wednesday, February 9, 2011 8:50:35 AM Subject: Re: HFS file questions An easy and reliable (at least I've found it so) is: /samples/copytree -a sourcedir targetdir Mount a new HFS at a "targetdir", run copytree then unmount old and mount new, if that's doable in your circumstances. Whenever possible, I like to stick with OMVS copy methods when dealing with OMVS files rather than worry about DFDSS or FDRCOPY. Just a personal preference. Dick Bond Department of Information Services CSD Production Support [email protected] Notice: This document contains information about the infrastructure and security of the state of Washington’s computer and telecommunication networks. Please make every effort to control access to this document and the information within it. All or part of this document may be exempt from public disclosure pursuant to RCW 42.56.420 (1) and (4). Please immediately direct any requests for public disclosure of all or part of this document to the DIS public disclosure officer at: [email protected] > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Rob Schramm > Sent: Tuesday, February 08, 2011 7:30 PM > To: [email protected] > Subject: Re: HFS file questions > > Linda, > > In order to make sure you get a clean copy using FDRCOPY, you'll have > to either quiese or unmount the filesystem before doing the copy to a > new/backup data set. HFS is very intolerant of fuzzy copies. > > As for the expansion, this is way easier with zfs v.s. hfs. It has been a > while > since I have dealt with HFS... so maybe one of the other members knows > the answer. > > If there isn't an easy way.. then: > 1) make a new hfs/zfs file > 2) mount it somewhere like /u/temp > 3) there are various methods .. I have seen various documents indicating > use of pax. I have just run a cp command with recursive and preserve cp > -Rp. > > Rob > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
