CA Bundl collector (DPMB001) abends with U600, FBKWD code: AA0800D4

Document ID : KB000108882
Last Modified Date : 31/07/2018
Show Technical Document Details
Issue:
The CA Bundl collector task (pgm=DPMB001) abends with the following errors:

BND7002E DPMFSIF   I/O Funct: WRITE DIRECT      Descr: NO ERROR DESCRIPTION - SEE FBWD
BND7003E DPMFSIF       FBKWD: AA0800D4            Rec: 40E2E4D7D7D9C5E2E24040E2E4D7D7D9
BND7030E *  PROGRAM   = DPMB001                                                
BND7030E *  FUNCTION  = WRITE DIR                                              
BND7030E *  FILE NAME = DPMFSIF                                                
BND7030E *  KEY VALUE =  ABCDEFG...BEGPAGE   ..--.l.-V...9¨
BND7030E *  RETURN CD = 008          BUNDL RETURN CD = 016                     
BND7030E *  REASON CD = 212          BUNDL REASON CD = 000  VSAM IO ERROR      
BND7030E *  MESSAGE   = BNDL639 - UNKNOWN ERROR

Additionally, a review of the CA LSERV started task that services the CA Bundl files shows the following DUMP being generated at the time of the abend in the CA Bundl collector:

IEA794I SVC DUMP HAS CAPTURED:                         
DUMPID=123 REQUESTED BY JOB (LSRVTASK)                       
DUMP TITLE=VSAM DYNAMIC RPL DUMP - IDA019RI+075E FEEDBACK CODE: AA0800D4

 
Environment:
z/OS
 
Cause:
Based on the error codes that were received:

BND7003E * FBKWD: AA0800D4
BND7030E * RETURN CD = 008
                   * BUNDL RETURN CD = 016                     
BND7030E * REASON CD = 212

The indication from these specific errors is that the Control Interval size (CI size) for the INDEX portion of the file shown in the error (in this case the DMPFSIF file) was not sufficient enough to support the VSAM splitting function that occurs during the collection of reports. 
Resolution:
If the problem continues to occur, consider increasing the CI size for the INDEX portion of the file that received the error. We typically recommend doubling the size. 
 
To increase the CI size of a file, update the appropriate 'HLQ...PPOPTION' library control member used to allocate the file. And then run a "reorg" against the file (BACKUP - DELETE/DEFINE - REPRO) to create a new file with the increased CI size.

Example of what to change to increase the CI size of the INDEX portion of the CA Bundl DPMFSIF file...

A. Edit the following PPOPTION library control member:
 
EDIT     YOUR.HLQ.PPOPTION(CC50SIF)        
********************************* Top of Data *
    DELETE +                                   
            ('CAICC50.DPMFSIF') CLUSTER        
    DEFINE CLUSTER +                           
              (NAME('CAICC50.DPMFSIF') +       
              VOLUMES(SIFVOL) +                
              RECORDS(1000 200) +              
              RECORDSIZE(282 512) +            
              KEYS(48 1) +                     
              FREESPACE(40,5) +                
              SHR(2 3)  REUSE +                
              SPEED +                          
              INDEXED) +                       
         DATA (NAME('CAICC50.DPMFSIF.DATA') +  
              CONTROLINTERVALSIZE(6144)) +     
        INDEX (NAME('CAICC50.DPMFSIF.INDEX') + 
              CONTROLINTERVALSIZE(1024)) <------- CHANGE THIS VALUE FROM 1024 to 2048)       
******************************** Bottom of Data

B. Tailor and submit your "rerog" process to Backup, Delete, Define and REPRO the new file.

Note - CA Bundl provides a CC50JORG job (also located in the CA Bundl installed PPOPTION library) that can be used to perform the "reorg" process against a specific CA Bundl VSAM file. Be sure and tailor the jobs JCL to point to the specific file you are increasing the size of. 

 
Additional Information:
In order to be able to perform a REORG process against a CA Bundl VSAM file, the CA LSERV task as well as all other CA Bundl batch and online  applications will have to be shut down until the REORG has completed.