Reprint process abended with U0600 - RC=12 with BND7159I Archive data set is not cataloged

Products

• Bundl

Issue/Introduction

Programs executed during the reprint process = DPMB005,DPMB002,DPMB003,DPMB009,DPMB011)

You receive the following errors during batch CC50J005 reprint processing:

BND7001I CA-Bundl version: 5.0.00, level: 5.0.00 
BND7159I Archive data set hlq.BDLMTHLY.G0158V00 is not cataloged 
BND7161I Skipping to next RIF entry 
BND7156E Reprint pages missing from archive data set - pages bypassed 
BND7008I Job ended - return code 0012 
IEF142I <jobname> <stepname> - STEP WAS EXECUTED - COND CODE 0012 

16.01.38 JOB07330 IEF450I <jobname> DPMS600 <stepname> - ABEND=S000 U0600 REASON=00 
654 JOB-<jobname> JOBSTEP-<stepname> PROCSTEP-DPMS600 
654 PROGRAM-DPMS600 ABEND-U0600 
16.01.38 JOB07330 -<jobname> <stepname> FLUSH 0 0 .00 
16.01.38 JOB07330 <jobname>  <stepname> FLUSH 0 0 .00 
16.01.38 JOB07330 -<jobname> <stepname> FLUSH 0 0 .00 
16.01.38 JOB07330 -<jobname> <stepname> FLUSH 0 0 .00 
16.01.38 JOB07330 -<jobname> <stepname> FLUSH 0 0 .00 
16.01.38 JOB07330 IEF404I <jobname> - ENDED - TIME=16.01.38 
16.01.38 JOB07330 -<jobname> ENDED. NAME-IT-DATA - BUNDL TOTAL TCB CPU TIM 
16.01.38 JOB07330 $HASP395 <jobname> ENDED - ABEND=U0600

Environment

z/os

Cause

The Bundl documentation for the "BND7159I Archive data set dsname is not cataloged" message states the following: 

- BND7159I Archive data set dsname is not cataloged 

Action: 
If message BND7159I is not followed by BND7160I (BND7160I Replacement file for: dsname), you must catalog this data set. 

- The ABEND=U0600 is simply a generic abend that, in this case, is a consequence of the requested archive file not being in the MVS catalog.   

Resolution

The resolution to this problem will depend on whether or not the report data to be reprinted is possibly available by re-cataloging the missing GDG file (if it's tapes have not been overwritten) or, from a  DUPLICATE archive file.

1. Have your sites Storage/Tape management Administrators determine whether or not the tapes associated to the lost "HLQ.BDL000.BDLMTHLY.G0158V00" file have been overwritten or not. If you are able to determine that the tapes associated to the uncatalogued GDG file have NOT been overwritten,  the easiest resolution would be to have the Administrators simply RE-CATALOG that lost file.

2. If you are able to determine that the original tapes have been overwritten and/or are no longer available, you will want to check your daily archive process (CC50J004) and your consolidation processes (CC50J019) to see if you are creating DUPLICATE archive tapes.
 

Check your check your daily batch Bundl processes, and your End of Day cycle, and see where you are executing PGM=DPMB004. In that step, the //DPMFAPF DD statement is the one that creates your PRIMARY daily archive file. To determine if you are creating a DUPLICATE file as part of this process, see what you have coded on the //DPMFAPF2 DD Statement. This would be the DUPLICATE file. 

In the consolidation job (CC50J019), the //DPMFCPF DD statement creates the PRIMARY consolidated file. Check and see what you have specified on the //DPMFCPF2 DD statement. This would be the DUPLICATE archive consolidation file. 

If you are creating DUPLICATE archive files, you may be able to recover the report(s) from the DUPLICATE tapes. Possible resolutions include execution of the CC50J037 utility to replace the AIF pointers for the reports on the lost file with the AIF pointers to the reports on the DUPLICATE tapes. Or, possibly by using the DPMT987 table. 


3. Depending on whether or not the report data is available by cataloging the original tapes or recovering them from a DUPLICATE tape, if it is determined that the data is simply no longer available, then the report data that was on the "HLQ.BDL000.BDLMTHLY.G0158V00" file has been lost. As a consequence of this, you will have to followup on getting the AIF pointer records to the rpeorts that are on the lost file deleted out of the AIF in order to prevent future abends in the reprint process. You can delete the references to this particular archive file out of the AIF by executing the CC50J080 utility with the following parameters.

NOTE: CA suggests running the CC50J080 utility with FUNCTION=LIST first to get a listing of the reports that will be lost. Keep this listing for your records!!
 

CC50J080 utility parameters to LIST or DELETE the AIF pointers to the lost file are as follows...

INDEX=A** 

FUNCTION=DELETE      <<<<<-----  (NOTE: Use FUNCTION=LIST for REPORT only) 

DETPR=Y 
DSNME=fully.qualified.archive.dsn.G00V00