On 7/18/2021 3:32 AM, Paul Gilmartin wrote:
On Fri, 16 Jul 2021 18:59:03 -0700, Charles Mills wrote:
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.
Sounds like an RFE candidate. CSV should preserve the needed information
and provide an API to access it.
What about LPA? Original data set and member?
What should happen if the program object is replaced in the interim?
Yeah, but...
CSVQUERY gives you access to all that.
The only thing you can't find out is which library in the LPALST a
specific module in PLPA came from. With some poetic license (assume that
the LPALST libraries are cataloged and have not changed since CLPA time)
then you can search that yourself.
Also, GETMAINed chunks of storage which are subsequently declared as a
program to the system have no information about from whence they came.
If the provider is AOSL then you know it came from the program loader
and was not fetched directly from a data set.
For UNIX a pointer to the path name is available. If the UNIX program
has been replaced or deleted since then then I guess you can't go look
at it any more. For PDS/PDSE then you can compare the TTR (MLT) with the
TTR (MLT) in the PDS/PDSE to verify if it is the same if you really want
to obsess about it.
But most of the time you just want to know where it came from (whether
or not it is current, because presumably it was current at fetch time)
so most of that extra stuff can be ignored. Program size is also a good
ad hoc test for program level matching.
Cheers,
Greg
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
