We have detected that there are load members that were suppose to have been copied from an Endevor loadlib to another loadlib. Where an number of the load members in this 'other' loadlib are missing their LOADMOD FOOTPRINT. However the CSECT(s) within the load members (Cobol type) still have their footprint.
Can't think of what would cause this, beyond actually running an job which generates the load out side of Endevor but includes the object from an Endevor Object library.
What condition(s) using a copy process / common utility running out side of Endevor, could cause this to happen?
Example of load member intact:
A600CV10 *LOADMOD COMMON OLCOM OLCOM A600CV10 LNKC3C 2 0100 22MAR17 14:47
A6AMAX10 COMMON OLCOM OLCOM A6AMAX10 COBOL 2 0100 22MAR17 14:44
Same load member in a non Endevor load lib missing the *LOADMOD footprint:
A600CV10 A6AMAX10 COMMON OLCOM OLCOM A6AMAX10 COBOL 2 0100 22MAR17 14:44