Patching to prevent ABARS from automatically cleaning up residual versions of ABACKUP output files

If a failure occurs during a previous ABACKUP for an aggregate, it is possible that a residual ABACKUP output file is left over and was not cleaned up (usually due to an error condition). The ABACKUP processing normally detects this and deletes the residual file. If the ABACKUP processing detects an existing output files for the version currently being created, the ABACKUP function deletes the files.

To prevent the ABACKUP function from deleting the output files, issue the following PATCH command:

PATCH .ABRCB.+82 BITS(.1......)

If the patch is set on, ABACKUP processing issues the ARC6165E message, ABACKUP processing fails, and the user will have to manually delete or rename the files.