Clean up after COPYCAT FILECOPY Abend S322

Products

• CA 1 Flexible Storage
• CA 1 Tape Management - Copycat Utility
• CA 1 Tape Management - Add-On Options

Issue/Introduction

Performed a COPYCAT job and it abended with S322, as a work around the job was resubmitted with TIME=1440 to avoid having the job time out.

The question pertains to the failed COPYCAT generated tapes. Once the job abended it left two copies of the file that was being copied and due to the ABEND it never completed and it did not expire the initial tape.

Here is the Display of the file from CA1:

                                                                          VOLUME  FILE     EXPIRE            CREATE
CMD   DATA SET NAME                                   SERIAL   SEQ     DATE                 DATE 
           xxx.yyy.zzz.G0030V00                           C33451   00006   PERMANENT    2018/027
           xxx.yyy.zzz.G0030V00                           725087    00001   PERMANENT    2020/006

The question pertains to cleaning up the duplicate files. Is it necessary to manually scratch the new copy that was created on 2020/006 (725087), or just to re-run the COPYCAT job again on C33451 and upon successful completion will it clean up both C33451/725087?

 

Environment

Release : 14.0

Component : CA 1 Tape Management Copycat Utility

Resolution

Since FILECOPY ran with UNSTACK a lot of output tapes already had been created with EXPDT=PERMANENT.
As they were closed before the abend occurred the abend retention is not applied and they need to be expired manually.
I suggested to check for IECTMS9 or IEC205I messages to find the volumes, that had been created.

 

NOTE: as multvolume files had been created update the first volume only with EXPDT=ZEROS. This is required, as
the EXPDT is a multivolume field and updates to volumes sequence > 1 are rejected per default.
INDISP retention and RECATLG=PREV were not applied yet, so the input tape has not changed and FILECOPY can
just be rerun.

The suggestion would be to rerun the FILECOPY job first and after it has ended successfully, expire the volumes created
by the failed job manually. Just to be on the safe side.