Re: PSDS source informations availability

On 17-Jan-2014 09:37 -0800, Marco Benetti wrote:

I try to explain my goal. All my programs have to call a generic
program that returns some information based on the name of the source
from which the program was compiled. So I need the source
information at runtime.

Seems an odd design. What does the correlation of source member to run-time object achieve? What sort of effect comes from it?

This call need to be as fastest as possible, because it is in all my
programs, so I would like to avoid using an API to retrieve the
source info.

The API calls could be limited to those invokers that either do not pass the source-information or whereby the provided source-information identifies a QTEMP object name. The invoking executable can be presumed likely already to be in memory, so the longer code path would be an issue for the actual access to the run-time object, along with any paging for the API code [though it might also remain in memory]. Is there any strong evidence that the additional API work would be an impact worth the expressed concern; i.e. by actual tests?

Because any caller may be able to compose its own information to pass [not restricted to the PSDS source-information variables likely, per even possibly being values generated into the source], is there any concern for a program spoofing another; i.e. passing information from the source of a different program? Seems the API approach for all invokers would eliminate any spoofed invocations.