I was just comparing what you want with what TSO ISRDDN provides, if ISRDDN does it, you should be able to do it too. It was just my guess that ISRDDN uses CSVQUERY to get that information, I'm not sure how it does it, but I just did a quick test with CSVQUERY and it looks like the information you are looking for might be in OUTPDATA, the last full word of the 16 bytes has a pointer to a IEWLFMD.
I don't think that is the intended programming interface though, maybe someone else can help us here. Regards, Leo -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Support, DUNNIT SYSTEMS LTD. Sent: Wednesday, January 27, 2016 12:18 PM To: [email protected] Subject: Re: Need to find the DSN from where load module was loaded Hello Leondardo, In this case, we can exclude the LINKLST. Since this is also applicable to a batch job environment and we're talking about during actually execution time, TSO ISRDDN is not applicable. Looking at the CSVQUERY macro documentation, am I correct in assuming this will NOT give me what I need under the circumstances? Or is the CSVQUERY macro my direct ticket to finding the DSN of the program brought into storage by a LOAD in both batch and ISPF environments? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
