VALIDATE function of the UNLOAD/RELOAD/VALIDATE utility (C1BM5000) flagged several elements with footprint errors as the members were missing from the base library. For example:
C1G0030E UNABLE TO VERIFY FOOTPRINT FOR ELEMENT IN THE ELEMENT BASE LIBRARY
C1G0014E DATA SET/FILE NOT FOUND
It also wrote DELETE actions intended to get rid of the corrupted elements to the dataset allocated to C1SCL1 DD
However, these DELETE actions, when executed, raise the same exact footprint errors.
Release : 18.0
Component : Endevor Software Change Manager
This is correct and expected behavior.
The programs that process the DELETE actions are not aware of the fact that the elements are corrupted and try to reach their (non-existent) base/delta members anyway, which raises the footprint errors.
However, the DELETE actions proceed, delete whatever members are found and also delete the element records from the MCF so that the corrupted elements are in fact removed from endevor.
For example this will delete the Element. The message SMGR112I indicated the element was deleted from the MCF.
C1G0030E UNABLE TO VERIFY FOOTPRINT FOR ELEMENT IN THE ELEMENT BASE
C1G0030I AT LOCATION: ENV: <env>, STG: <stage>, SYS: <system>, SBS: <subsystem>, TYP <type>
C1G0000I DATA SET <Dataset>
C1G0000I MBR/FILE <member>
C1G0014E DATA SET/FILE NOT FOUND
C1G0030E UNABLE TO VERIFY FOOTPRINT FOR ELEMENT IN THE ELEMENT <element>
C1G0030I AT LOCATION: ENV: <env>, STG: <stage>, SYS: <system>, SBS: <subsystem>, TYP <type>
C1G0000I DATA SET <dataset>
C1G0000I MBR/FILE <member>
C1G0014E DATA SET/FILE NOT FOUND
SMGR112I ELEMENT VVLL 0100 DELETED FROM LOCATION<env>/<stage>/<system>/<subsystem>/<type>
C1G0277I DELETE PROCESSING TERMINATED BECAUSE OF THE PREVIOUS ERROR
C1G0200I ELEMENT ACTION REQUEST PROCESSING COMPLETED, HIGHEST ENDEVOR RC = 0012
END OF EXECUTION LOG - HIGHEST ENDEVOR RC = 0012