Thanks Alan;
The FLASHCOPY command was exactly what we needed, and works perfectly. Where
building a system with two 3390 mod 9 disks took about 18 minutes using DDR
for the copy, using FLASHCOPY produces a bootable system in 41 seconds.
Quite an improvement.
In the CONFIG DATADVH file, the description of the FlashCopy Behavior is as
follows:
/*!DVHDXD_FLASHCOPY_BEHAVIOR= n */
/*! Specifies whether DATAMOVE uses DDR (if 0), synchronous */
/*! FLASHCOPY (if 1), or asynchronous FLASHCOPY (if 2). */
/*! The default is 2. */
But, in the documentation for the FLASHCOPY CP command, if FlashCopy version
2 hardware is in use, then all the commands are synchronous, no matter what
the request was. The difference would only be noticed on FlashCopy version 1
hardware, where it could be done either way. This is likely why the
discrepancy hasn't been noticed, or made much difference.
Thanks for pointing me in the correct direction. You all are like having a
z/VM GPS....
Standing on the shoulders of greatness...
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OE-5-55 200 First Street SW
/( )\ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
On 1/8/08 8:46 AM, "Alan Altmark" <[EMAIL PROTECTED]> wrote:
>
> I think there is an error in the doc. The default level 2 behavior is
> (supposed to be) synchronous. DirMaint will poll, waiting until the
> flashcopy is complete before reporting "Done".
>
> Level 1 causes DirMaint to issue the CP FLASHCOPY command (without the new
> SYNCH option). The CP FLASHCOPY command is yours to play with, too, but
> you need class B.
>
> Please contact the Support Center so that we can get to the bottom of
> things.
>
> Alan Altmark
> z/VM Development
> IBM Endicott
