On Wed, 19 Mar 2008 08:49:16 -0500, Arthur Gutowski <[EMAIL PROTECTED]> wrote:

>On Tue, 18 Mar 2008 12:06:57 -0700, Schwarz, Barry A
><[EMAIL PROTECTED]> wrote:
>
>>ADRDSSU used to have problems copying HFS datasets (the workaround was
>>DUMP/RESTORE in place of COPY).  I don't know if it still does.  I have
>>never successfully copied a spool dataset and always had to reformat.  I
>>never tried to copy a page dataset since it was always easier just to
>>allocate a new one.
>
>We routinely use FDR to copy HFS datasets in our migration/clone process,
>but dss works just as well.  Use LOGICAL instead of PHYSICAL copy so that
>dss issues a QUIESCE for an open (mounted) filesystem.  For FDR, specify
>HFS=QUIESCE.  Otherwise, if the HFS is mounted R/W, you almost certainly
>will have a corrupt copy.
>

Note that if you are using zFS that HFS=QUIESCE does not work with FDR. 
I had to add a zfsadm quiesce and unquiesce steps and change my copy 
step in my clone JCL to use "DSNENQ=NONE,ENQERR=NO" when I 
migrated my maintenance unix files to zFS.  This is because my 
maintenance unix files are always mounted at a service mount point.
If you don't keep them mounted, this is not a consideration.

I spoke to Innovation about this and they couldn't give me any time frame
when FDR would be fixed / enhanced to do this.   There is a way to get it
to work with EMC / snap, but it is much to convoluted for my taste.  Adding
the zfsadm step was much simpler and easier to understand.

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

Reply via email to