Thanks, Walt. > it can only tell for a subset of the cases
I (the OP) would just like to maximize the size of that subset, or more accurately, I would like to exploit all of the available subset. It's not a "load library reporting program" that would have to cover 99% of the cases to be useful. It's a part of a feature for a product that has nothing in particular to do with load libraries, and therefore, a defined and documented "subset" feature will be fine. I just want to maximize the subset. Thanks for everyone's assistance. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Walt Farrell Sent: Tuesday, August 16, 2005 9:38 AM To: [email protected] Subject: Re: How tell name of originating load library? On 8/16/2005 11:46 AM, [EMAIL PROTECTED] wrote: > Wouldn't it be possible to front-end the LOAD-, LINK-, ATTACH-, > XCTL-SVCs etc. to get the necessary associaton from the DCB to the > DSN? > Yes, but after then, from the module itself (for some general module not part of your product that does the hooking) how do you find out where it came from. Someone already said earlier in this thread (I think) that Contents Supervision -could- save all the necessary information, but it doesn't. And yes, some other product -could- save all the necessary information, and create a query interface that would return it. But the question under consideration is, in today's environment, how can a program tell with certainty where it was loaded from. And the answer is that it can only tell for a subset of the cases, because the system does not save enough information to provide the answer in the rest of the cases. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
