Re: Easiest way, in a CL pgm, to find out what source member a programwas compiled from?

Thanks for the suggestions, and for letting me know early-on, that there wasn't anything out there I was missing, that would have been easier than what I ended up doing.

I came up with something. And managed to do it all in a single OPM CL pgm.

First, I call QCLRPGMI, on the off-chance that it's an OPM program. If the source information is nonblank, I'm done.

If it's blank, then I create a user space in QTEMP (it's remarkable how callable system APIs are from CL!), then I call QBNLPGMI, pouring into that user space.

Then I call QUSRTVUS of 4 bytes at position x'0000007D' (7C + 1), add 1 to the 4-byte binary value I find there (that "%BIN" function/pseudovariable is remarkably useful), do another QUSRTVUS at that position (with a length of x'00000046') and pull the source information from the first module (given that any additional modules in the programs we're interested in would have been pulled in from a binding directory listed on an H-spec, we can be reasonably sure that the entry-point module is the first one linked, and since they're guaranteed to be returned in the order linked, we know it's the one we want).

--
JHHL