When executing CA FAVER RESTORE I see multiple IDCAMS messages in the job output. Can these be explained?
search cancel

When executing CA FAVER RESTORE I see multiple IDCAMS messages in the job output. Can these be explained?

book

Article ID: 45392

calendar_today

Updated On:

Products

FAVER VSAM Data Protection for z/OS

Issue/Introduction

Question:

When executing CA FAVER EXPORT and RESTORE I see multiple IDCAMS messages. Why do we see these and what are they telling us?

Answer:

You should never see EXPORT processing producing IDCAMS messages unless there is a catalog error. You should see the following or something very similar, these are the basic messages expected from an EXPORT:

GV131 DDNAME=FVROUT0, EXPORT COMPLETE TO DSN=prefix.FAVER45.EXPORT VOL=TSU127  
       1 OBJECTS SUCCESSFULLY PROCESSED                                      
       0 UNSUCCESSFUL                                                        
********** END OF JOB                                                        

During a RESTORE you will see IDCAMS messages in every execution. CA FAVER uses IDCAMS to define the VSAM files being restored. You can expect something similar to these:

GV831 DDNAME=FVRIN0, RESTORING FROM DSN=MFLVOL.BKUP.FAVER52 VOL=TSU127  
    PUBLIC.$RBTEST3 -  EXPORTED 08-AUG-16.221 12:59:45 - START 08-AUG-16
                                                                        
           DEL (PUBLIC.$RBTEST3                                         
          IDC0550I ENTRY (D) prefix.$RBTEST3.DATA DELETED               
          IDC0550I ENTRY (I) prefix.$RBTEST3.INDEX DELETED              
          IDC0550I ENTRY (C) prefix.$RBTEST3 DELETED                    
          IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0        

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 
                                                                  
 DEF CL( -                                                        
        NAME(PUBLIC.$RBTEST3                             ) -      
        IXD -                                                     
        STORCLAS (TSO     ) -                                     
        MGMTCLAS (TSO     ) -                                     
        DATACLAS (DCWRKD  ) -                                     
        ) -                                                       

 etc... for the standard DEFINE process.

You will also see the following similar messages:

                  )                                                            
          IGD01008I ALLOCATION SET TO TSO M3280                                
          IGD01010I ALLOCATION SET TO SGTSO STORAGE GROUP                      
          IDC0508I DATA ALLOCATION STATUS FOR VOLUME TSU015 IS 0               
          IDC0509I INDEX ALLOCATION STATUS FOR VOLUME TSU015 IS 0              
          IDC0181I STORAGECLASS USED IS TSO                                    
          IDC0181I MANAGEMENTCLASS USED IS TSO                                 
          IDC0181I DATACLASS USED IS DCWRKD                                    
          IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0            
                                                                               
          IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0    
         EXIT RECORD COUNTS INPUT=739 RESTORED=739 DELETED=0 MODIFIED=0 INSERTED
         739 RECORDS                                   - END   08-AUG-16 12.59.4
RESTORED...                                                                    
     1 SUCCESSFUL                                                              
              CA-FAVER  -  END OF JOB  -  HIGHEST CONDITION CODE WAS 0         

Since all of these are IDCAMS messages you can see where CA FAVER is defining the file exactly as the file was exported.

 

Additional Information:

If you receive catalog errors or RESTORE errors the IDCAMS messages generated under the cover of CA FAVER are passed back into the output. A recommendation would be to run an IDCAMS DIAGNOSE to ascertain of there was an error.    

 

Environment

Release: FASTDA00200-4.5-CA-FastDASD
Component: