Multiple IDCAMS messages in the job output when executing FAVER RESTORE

Products

• FAVER VSAM Data Protection for z/OS

Issue/Introduction

When executing FAVER EXPORT and RESTORE there are multiple IDCAMS messages. 

 

 

Environment

Release: 4.5 
Component: FastDASD

Resolution

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=TSUXXX   
       1 OBJECTS SUCCESSFULLY PROCESSED                                      
       0 UNSUCCESSFUL                                                        
********** END OF JOB                                                        

During a RESTORE you will see IDCAMS messages in every execution.  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=TSUXXX   
    PUBLIC.$XXXXXXX -  EXPORTED 08-AUG-16.221 12:59:45 - START 08-AUG-16
                                                                        
           DEL (PUBLIC.$XXXXXXX                                          
          IDC0550I ENTRY (D) prefix.$XXXXXXX.DATA DELETED               
          IDC0550I ENTRY (I) prefix.$XXXXXXX.INDEX DELETED              
          IDC0550I ENTRY (C) prefix.$XXXXXXX DELETED                    
          IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0        

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 
                                                                  
 DEF CL( -                                                        
        NAME(PUBLIC.$XXXXXXX                             ) -      
        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 MXXXX                                 
          IGD01010I ALLOCATION SET TO SGTSO STORAGE GROUP                      
          IDC0508I DATA ALLOCATION STATUS FOR VOLUME TSUXXX IS 0               
          IDC0509I INDEX ALLOCATION STATUS FOR VOLUME TSUXXX 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 FAVER is defining the file exactly as the file was exported.

 

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