Endevor

Expand all | Collapse all

Under what condition(s) would copying a load member in an external job cause the LOADMOD FOOTPRINT to disappear while still having the CSECT(s) (OBJECT(s) FOOTPRINT?

  • 1.  Under what condition(s) would copying a load member in an external job cause the LOADMOD FOOTPRINT to disappear while still having the CSECT(s) (OBJECT(s) FOOTPRINT?

    Posted May 24, 2017 02:31 PM

    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



  • 2.  Re: Under what condition(s) would copying a load member in an external job cause the LOADMOD FOOTPRINT to disappear while still having the CSECT(s) (OBJECT(s) FOOTPRINT?

    Posted May 24, 2017 02:45 PM

    Hi Ron, I have seen this when converting from a PDS to PDS/e using IEBCOPY or other copy utilities.  Using Endevor BSTXCOPY keeps all the footprints. -Phil

     

     

    https://communities.ca.com/thread/241696336



  • 3.  Re: Under what condition(s) would copying a load member in an external job cause the LOADMOD FOOTPRINT to disappear while still having the CSECT(s) (OBJECT(s) FOOTPRINT?

    Posted May 24, 2017 02:59 PM

    Thought of that but the files that are involved or at least the ones I know of are PDS.



  • 4.  Re: Under what condition(s) would copying a load member in an external job cause the LOADMOD FOOTPRINT to disappear while still having the CSECT(s) (OBJECT(s) FOOTPRINT?
    Best Answer

    Broadcom Employee
    Posted Jun 01, 2017 02:26 PM

    Hi,

    From what you are saying you are trying to copy a PDS to PDS or PDSE to PDSE loads.

     

    You can use IEBCOPY or the like to do a copy.

    The time you must use BSTCOPY/BSTXCOPY is to convert between PDS and PDSE. PDS and PDSE are different in the way they  store the footprint.  The utilities  execute BSTCOPY/BSTXCOPY the binder to change the footprint format.

    Remember that if the member is copied outside of the Endevor processor the component list will not be updated on the new additional location.