Withdrawing a FlashCopy® relationship differs widely between FlashCopy V1 and FlashCopy V2 with FlashCopy V2 providing more options. The FlashCopy relationship being withdrawn can be one in FlashCopy COPY mode that has not completed the background copy, or one in FlashCopy NOCOPY mode that requires that you to issue a FCWITHDR command to end the relationship.
For any other situation other than a request syntax problem (that is, parameters in error), the FCWITHDR request will be reported as successful regardless of the status of the specified tracks.
The FlashCopy withdraw process removes any existing FlashCopy relationship. The FlashCopy withdraw process locates source tracks on the source device and target tracks on the target device, and ends the FlashCopy relationship between them.
You cannot specify extent sets on the FlashCopy V1 withdraw request. Thus, a FlashCopy withdraw process defaults to a full volume withdraw operation of the specified source and target devices.
In order to withdraw a FlashCopy relationship between open (FB) devices, the CKD access device must be specified and only full volume relationships can be withdrawn.
When withdrawing a FlashCopy inband relationship, the subsystem that was specified for SSID on the PPRC establish pair command must be identified. Only full volume relationships can be withdrawn.
Tracks may be copied from the source to the target volume even if the source track is not changed. This includes the track that contains the volume label. Therefore, to avoid duplicate volume serial problems when the target device is later varied online, IBM® recommends that you relabel the target volume after withdrawing a volume-level FlashCopy NOCOPY relationship.