Explanation
The FlashCopy® withdraw is not performed because of a
failure indicated by the reason code. The possible reason codes (reason_code)
are:
- 1
- The dump of the volume or data set is unsuccessful.
If the data set is a cluster or an
alternate index in a sphere and sphere processing is being done for this data set, the FlashCopy relationship could not be withdrawn because a
cluster or an AIX® that is part of a sphere was not
successfully processed.
- 2
- DFSMSdss cannot obtain storage to
perform the withdraw for the data set or volume.
- 4
- DFSMSdss cannot exclusively enqueue
on the data set.
System action
The FlashCopy withdraw is not issued. If the volume
or data sets were in a FlashCopy relationship, the FlashCopy relationship still exists. The return code is
4.
Operator response
Programmer response
Take the following actions depending on the reason code:
- 1
- Previously issued messages describe the failures that occurred during the dump process. Correct
the errors and rerun the dump job, specifying the FCWITHDRAW keyword. If a successful dump cannot be
taken and you still want to withdraw the FlashCopy
Relationship, use the TSO FCWITHDR command to withdraw the FlashCopy relationship.
- 2
- Provide adequate storage by increasing either the REGION size, the SIZE parameter, or both, or
specify the filtering criteria to reduce the number of data sets for operation. Rerun the job, See
z/OS DFSMSdss Storage Administration for more information about storage
estimates.
- 4
- Use the TSO FCWITHDR command to withdraw the FlashCopy relationship. See z/OS DFSMS Advanced Copy Services for more information about FlashCopy TSO
commands.
Guideline: Be aware that any FlashCopy
relationship established since the COPY or DUMP operation is affected by the TSO FCWITHDR
command
Source