Endevor Unload failing with C1G0030E and C1G0014E errors

Products

• Endevor
• Endevor - Enterprise Workbench

Issue/Introduction

During the  weekly Endevor Unload the following errors occured - what can be done to resolve them? 


           09:31:05  C1G0030E  UNABLE TO VERIFY FOOTPRINT FOR ELEMENT IN THE ELEMENT BASE LIBRARY
           09:31:05  C1G0030I    AT LOCATION:  ENV: xxxxxxxx, STG: x, SYS: xxxxxxxx, SBS: xxxx, TYPE: xxxx
           09:31:05  C1G0000I     DATA SET iprfx.iqual.STAGE1.BASE.JCL 
           09:31:05  C1G0000I     MBR/FILE xxxxxxxx
           09:31:05  C1G0014E  DATA SET/FILE NOT FOUND
           09:31:05  C1G0030E  UNABLE TO VERIFY FOOTPRINT FOR ELEMENT IN THE ELEMENT DELTA LIBRARY
           09:31:05  C1G0030I    AT LOCATION:  ENV: xxxxxxxx, STG: x, SYS: xxxxxxxx, SBS: xxxx, TYPE: xxxx
           09:31:05  C1G0000I     DATA SET iprfx.iqual.STAGE1.DELTA.JCL 
           09:31:05  C1G0000I     MBR/FILE xxxxxxxx
 
                                       E N D E V O R   U N L O A D   E X E C U T I O N   L O G

           09:31:05  C1G0014E  DATA SET/FILE NOT FOUND
           09:31:05  C1G0000I     ELEMENT xxxxxxxx
           09:31:05  C1R5308I  LOCATION: SYS: xxxxxxxx SBS: xxxx TYPE: xxxx (17) STG: STAGE1
  

Environment

All Supported Releases

 

Resolution

The C1G0030E message is always associated with the C1G0030I message which will give one the Endevor inventory location for where the problem resides.

C1G0030E UNABLE TO VERIFY FOOTPRINT FOR ELEMENT IN THE ELEMENT BASE LIBRARY
C1G0030I AT LOCATION: ENV: xxxxxxxx, STG: 1, SYS: xxxxxxxx, SBS: xxxx, TYPE: xxxx
C1G0000I DATA SET iprfx.iqual.STAGE1.BASE.JCL
C1G0000I MBR/FILE xxxxxxxx
C1G0014E DATA SET/FILE NOT FOUND

With the information at hand one can go into Endevor and do a footprint display on the library will the problem is reported to confirm the problem.

To correct the problem:

• If it is a problem with an element first check to see if a Source output library exists and the member is there, if it is, copy the member to a library outside of Endevor and then delete the member and re-add it.
• If there is not SOL and the problem is in the Delta library, check to if the base library is a reverse unencrypted library. If yes, copy the member from the base to a library outside of Endevor, delete the member from Endevor and re-add.
• If the steps above are not available, check your archive files and after deleting the element in Endevor transfer the element from the archive file to Endevor.
• If the problem is in the component, do a delete component only and regenerate the element in Endevor.