Endevor

  • 1.  Display of Load Module Footprints in the “Library Selection List” panel.  

    Posted Sep 24, 2017 09:50 PM
      |   view attached

    I’m looking to get foot printing of load modules correctly implemented in all of our processors. The problem (or not) that I have is that using option 1;1;2 (Display, Footprint) for a load module library, I only see member names displayed, but no footprint information. I then need to use option I to “Display load module CSECTS and Footprints” as indicated on the screen. (Panelid=C1SD4100).

    This behaviour differs from PDS/PDSE’s used for other types (e.g. Parm) where the footprint information is displayed.

    I’m interested to know if what I am experiencing is a feature or Endevor (Version 18.0.08) or the result of some ISPF customisation that is preventing the display of the footprint information on this screen.

    Would someone please advise me if it is possible to get a load module footprint to display in this panel, and if it is, perhaps give me some idea where to start looking for the reason that I am unable to see this on our system.

    Thanks very much.

    Attachment(s)



  • 2.  Re: Display of Load Module Footprints in the “Library Selection List” panel.  

    Broadcom Employee
    Posted Sep 25, 2017 07:19 AM

    Hi Franck,

     

    When displaying the Loadlib are you doing and "I" against the member to see the footprint because load module footprints are internal(*LOADMOD, CSECT), not in the directory like source members.

     

    Regards,

    Ollivier



  • 3.  Re: Display of Load Module Footprints in the “Library Selection List” panel.  

    Posted Sep 25, 2017 07:32 PM

    Hi Ollivier,

     

    Yes that is what I am doing. I have included an example in the attachment.

     

    I now understand from your comment " load module footprints are internal(*LOADMOD, CSECT), not in the directory like source members." that our system is functioning correctly and that the footprint cannot be displayed from the directory because it is not stored there. 

     

    I've since found this little gem from the manual which explains why this is the way it is.

     

    "Note: Footprinting of the load module PDS directory is not allowed because this would

    compromise the ability of the load module to execute. For PDS load module footprints, a

    user update to the IDR or a zap applied to the load module compromises the footprint."

     

    Thanks for your response.

     

    Cheers

     

    Frank