Explanation
Copy pool
cpname was determined
to be ineligible for processing.
- Retcode
- Meaning
- 2
- The generation 0 backup copy does not exist or did not complete
successfully.
- 3
- Automatic Dump processing failed for this copy pool because the
version to be dumped is a NOCOPY version where the Allow Fast Reverse
Restore option was specified in the copy pool definition during the
backup or is a version where a Fast Reverse Restore is partially processed.
These types of Fast Replication backup versions are not supported
by this function on this release of DFSMShsm.
- 4
- The generation 0 backup copy has already been successfully dumped.
- 6
- Frequency setting not met for any of the dump classes to which
copy pool cpname should be dumped.
- 8
- Another DFSMShsm function
was processing the copy pool identified in the message.
- 10
- An enqueue error occurred.
System action
DFSMShsm Autodump processing continues.
Programmer response
Determine why the copy pool is not eligible
for auto dump processing, and if necessary, take the following actions.
- Retcode
- Response
- 2
- If necessary, issue a FRBACKUP COPYPOOL(cpname)
command to create a complete backup of copy pool cpname.
Specify the DUMP keyword on the command to create a dump immediately
after the backup copy is made.
- 3
- Issue a dump request for this version on a release of DFSMShsm which
supports this backup version type.
- 4
- No action necessary.
- 6
- Review the frequency settings of the dump classes assigned to
copy pool cpname. If necessary, change the frequency
setting of one or more dump classes to ensure that copy pool cpname is
dumped during the auto dump window.
- 8
- If necessary, issue the FRBACKUP COPYPOOL (cpname)
DUMPONLY command to create a dump of the most recent backup version
of the copy pool.
- 10
- Contact IBM support