The print idea is feasible, but a little too much overhead.  The API
approach is better, but as you say, it's a bit of work.  Thanks for the
suggestions.

Joe


> -----Original Message-----
> From: Jeff Bull
>
> Hi Joe,
>       the program+library information you require is in your job data, the
> program stack.  It would surely be an easy task to write a small
> CL utility
> to print the program stack, copy it to a PF, then read through the PF
> looking for the program name (a passed parameter?) and to return
> the library
> name.  There is almost certainly a job-API that can help, but
> that may take
> a bit longer to get working.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.