Re: BLDL User Data
SMDE_NAME_OFF is the offset of the name. SMDE_PMAR_OFF is the offset of the PMAR. SMDE_PNAME_OFF is the offset of the primary name if this is a program object alias. The data returned by DESERV is not mapped by IHAPDS. The mapping of the DESERV output is clearly documented. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BLDL User Data
IGWDES? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joseph Reichman [reichman...@gmail.com] Sent: Sunday, August 20, 2023 4:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BLDL User Data Hi I used the FUNC=GET_ALL Still a little bit confused by the mapping returned I got a IGWDDESB it has a number of IGWSMDE's one for each member of the PDS the SMDE_NAME_OFF pointes to the offset of the first SMDE_NAME the SMDE_NAME_VAL is then mapped by IHAPDS ? that doesn't seem right after the name there is 3 bytes which could be a TTR and then looking at IHAPDS would be PDS2CNCT the concatenation number which in my case should be 0 but its not Just wondering if I am correct in that SMDE_NAME_OFF points to the first SMDE_NAME and that SMDE_NAME_VAL is mapped by IHAPDS thanks -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Sunday, August 20, 2023 9:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BLDL User Data What about FUNC=GET_NAMES? Which DESERV function are PDSE only and which work for PDS as well? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Peter Relson [rel...@us.ibm.com] Sent: Sunday, August 20, 2023 8:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BLDL User Data If you have only the primary name, for a PDS your only approach to finding all the aliases is to read the whole directory. DESERV FUNC=GET_ALL can be a nice way to do this. IHAPDS maps the PDS directory entry. IGWSMDE/IEWPMAR maps the PDSE directory entry. PDS2ALIS for the former, SMDE_Flag_Alias for the latter. The directory entry for an alias has the associated primary name. For a PDSE, there might be binder interface that will return to you the aliases (because the program object has a section that includes the names of all the aliases). Peter Relson z/OS Core Technology Design -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BLDL User Data
Got it had to initialize the header Still got some questions the IGWSMDE mapping the name offset points to SMDE_NAME DSECT and SMDE_NAME_VAL is mapped by IHAPDS that does seem right thanks -Original Message- From: IBM Mainframe Discussion List On Behalf Of Peter Relson Sent: Sunday, August 20, 2023 8:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BLDL User Data If you have only the primary name, for a PDS your only approach to finding all the aliases is to read the whole directory. DESERV FUNC=GET_ALL can be a nice way to do this. IHAPDS maps the PDS directory entry. IGWSMDE/IEWPMAR maps the PDSE directory entry. PDS2ALIS for the former, SMDE_Flag_Alias for the latter. The directory entry for an alias has the associated primary name. For a PDSE, there might be binder interface that will return to you the aliases (because the program object has a section that includes the names of all the aliases). Peter Relson z/OS Core Technology Design -- 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
Re: BLDL User Data
Hi I used the FUNC=GET_ALL Still a little bit confused by the mapping returned I got a IGWDDESB it has a number of IGWSMDE's one for each member of the PDS the SMDE_NAME_OFF pointes to the offset of the first SMDE_NAME the SMDE_NAME_VAL is then mapped by IHAPDS ? that doesn't seem right after the name there is 3 bytes which could be a TTR and then looking at IHAPDS would be PDS2CNCT the concatenation number which in my case should be 0 but its not Just wondering if I am correct in that SMDE_NAME_OFF points to the first SMDE_NAME and that SMDE_NAME_VAL is mapped by IHAPDS thanks -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Sunday, August 20, 2023 9:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BLDL User Data What about FUNC=GET_NAMES? Which DESERV function are PDSE only and which work for PDS as well? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Peter Relson [rel...@us.ibm.com] Sent: Sunday, August 20, 2023 8:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BLDL User Data If you have only the primary name, for a PDS your only approach to finding all the aliases is to read the whole directory. DESERV FUNC=GET_ALL can be a nice way to do this. IHAPDS maps the PDS directory entry. IGWSMDE/IEWPMAR maps the PDSE directory entry. PDS2ALIS for the former, SMDE_Flag_Alias for the latter. The directory entry for an alias has the associated primary name. For a PDSE, there might be binder interface that will return to you the aliases (because the program object has a section that includes the names of all the aliases). Peter Relson z/OS Core Technology Design -- 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
Re: BLDL User Data
On Sun, 20 Aug 2023 13:05:39 +, Seymour J Metz wrote: >What about FUNC=GET_NAMES? Which DESERV function are PDSE only and which work >for PDS as well? > And which, if any, work for allocated UNIX directories as BLDL does? I noticed that when I bound a program object with SYSLMOD allocated to a UNIX directory, aliases appeared as links. I didn't investigate whether the "alias" links persisted after I removed the principal object, nor whether invoking by an alias name started at the corresponding ENTRY address. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BLDL User Data
What about FUNC=GET_NAMES? Which DESERV function are PDSE only and which work for PDS as well? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Peter Relson [rel...@us.ibm.com] Sent: Sunday, August 20, 2023 8:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BLDL User Data If you have only the primary name, for a PDS your only approach to finding all the aliases is to read the whole directory. DESERV FUNC=GET_ALL can be a nice way to do this. IHAPDS maps the PDS directory entry. IGWSMDE/IEWPMAR maps the PDSE directory entry. PDS2ALIS for the former, SMDE_Flag_Alias for the latter. The directory entry for an alias has the associated primary name. For a PDSE, there might be binder interface that will return to you the aliases (because the program object has a section that includes the names of all the aliases). Peter Relson z/OS Core Technology Design -- 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
Re: BLDL User Data
If you have only the primary name, for a PDS your only approach to finding all the aliases is to read the whole directory. DESERV FUNC=GET_ALL can be a nice way to do this. IHAPDS maps the PDS directory entry. IGWSMDE/IEWPMAR maps the PDSE directory entry. PDS2ALIS for the former, SMDE_Flag_Alias for the latter. The directory entry for an alias has the associated primary name. For a PDSE, there might be binder interface that will return to you the aliases (because the program object has a section that includes the names of all the aliases). Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BLDL User Data
DESERV will do the job for PDSE; I suspect that it will work for PDS as well. You can contact me at work if you have questions. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joseph Reichman [reichman...@gmail.com] Sent: Friday, August 18, 2023 5:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: BLDL User Data 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
Re: BLDL User Data
Yes, each alias entry includes the member name and they all have the same TTR. You can use DESERV to get all of them in one swell foop, at least for PDSE; I suspect that it works for PDS as well. Note concatenation restrictions. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tom Marchant [000a2a8c2020-dmarc-requ...@listserv.ua.edu] Sent: Friday, August 18, 2023 8:11 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BLDL User Data IIRC there is only entry point in a directory entry for a load library. Other entry points would be in alias directory entries if there are any. -- Tom Marchant On Fri, 18 Aug 2023 17:28:32 -0400, Joseph Reichman wrote: >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 -- 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
Re: BLDL User Data
Why not let DESERV do the heavy lifting? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Dave Kreiss [davekre...@gmail.com] Sent: Saturday, August 19, 2023 6:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BLDL User Data 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 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 >> 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BLDL User Data
On a PDSE a binder of IEFBR14 with alias BR14 then bind of IEFBR14 no alias and BR14 alias was gone. Use 3.1 on the real member of first bind of IEFBR14 removed alias. Didn’t try to see what happens with 3.1 delete of alias. PDSE orphaning of alias appears to be addressed at least in ISPF and binder. 3.1 on PDS to delete real member leaves alias of BR14 as does above binder test on PDS. Alias points at previous IEFBR14 TTR such that TTR of new IEFBR14 is different than orphaned BR14. All run on z/OS 2.5. > On Aug 19, 2023, at 6:08 PM, Paul Gilmartin > <042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > > On Sat, 19 Aug 2023 17:14:41 -0500, Dave Kreiss wrote: > >> ... 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. >> > Did that change with PDSE? > > -- > gil > > -- > 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
Re: BLDL User Data
On Sat, 19 Aug 2023 17:14:41 -0500, Dave Kreiss wrote: >... 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. > Did that change with PDSE? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BLDL User Data
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 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 >> 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
Re: BLDL User Data
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 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
Re: BLDL User Data
IIRC there is only entry point in a directory entry for a load library. Other entry points would be in alias directory entries if there are any. -- Tom Marchant On Fri, 18 Aug 2023 17:28:32 -0400, Joseph Reichman wrote: >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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
BLDL User Data
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
