Alias entry points have separate directory entries. The alias directory entries have a flag bit on (I remember there is a DSECT IHAPDS or similar name) which indicate that this directory entry is an alias and also may have a different entry point address than the real or other alias members You need to match the TTR of alias to members the real member by running through all directory entries. If the real member is deleted but not all alias(s), those alias(s) are orphaned member(s) but the tensing member(s) data (load module) still exist. In this case knowing the real member name is not possible except if you know history of load module or maybe have backup or some other history like binder output or maybe job JCL. You’re the sleuth.
> On Aug 19, 2023, at 4:48 PM, Attila Fogarasi <fogar...@gmail.com> wrote: > > Take a look at PDS2EPM > https://www.ibm.com/docs/en/zos/2.1.0?topic=areas-pds-directory-entry-format-returned-by-bldl > > >> On Sat, Aug 19, 2023 at 7:29 AM Joseph Reichman <reichman...@gmail.com> >> wrote: >> >> Hi >> >> >> >> Just looking the user data I got from a BLDL specifically the entry name I >> have multiple (4) entry points the BLDL returned the entry /offset in the >> last entry for PDS2EPA using IHAPDS to map the returned data >> >> >> >> Was wondering if there was a way to get the other entry points >> >> >> >> Thanks >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
