Yeah, it is one of those problems that seems like it should have a simple answer "what DSN was this module loaded from? How hard is that?" but in reality has unlimited subtleties.
If you care, I think you have to use BLDL and keep track yourself. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Michael Stein Sent: Friday, July 16, 2021 6:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Concatinated datasets On Fri, Jul 16, 2021 at 06:13:13PM -0400, Bob Bridges wrote: > Wait, am I missing something? I have a REXX that takes a module name and DD > name and searches in the DD to tell me where it first finds that module. Is > that not reliable? It may be reliable for where a future fetch would find the module but it doesn't tell you where a module already in storage came from. Perhaps it was loaded with DCB= from some other file which isn't open or allocated anymore? Perhaps it is duplicated in the concatenation and someone did something funky with the DE= operand Z (concatenation) value and loaded the 2nd one (bit of a problem to get the rest of the BLDL info needed). Perhaps it's the result of an IDENTIFY. Or something else? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
