[Info-vax] How much of VMS is still in MACRO-32?

[hb]

On 6/2/21 4:31 PM, Arne Vajhøj wrote:
> On 6/2/2021 10:03 AM, Jan-Erik Söderholm wrote:
>> Den 2021-06-02 kl. 15:08, skrev Arne Vajhøj:
>>> On 6/1/2021 9:34 PM, Craig A. Berry wrote:
>>>> On 6/1/21 12:33 PM, Stephen Hoffman wrote:
>>>>> On 2021-06-01 15:27:34 +0000, Marc Van Dyck said:
>>>>>> Don't you do that with Source Code Analyzer, for languages that
>>>>>> support it ?
>>>>
>>>>> I use DECset SCA and PCA only  rarely, as few sites have licenses for
>>>>> that. Which means using symbol tables and maps, and the debugger,
>>>>> and  preferably refactoring where permitted.
>>>>
>>>> And as far as I remember PCA doesn't work on shareable images, which
>>>> means on any kind of application with a semi-modern architecture, you
>>>> either do without
>>>
>>> Would it ignore the time spent in the shareable image or would it just
>>> count it as being spent in the calling code?
>>
>> Hm... Aren't the code in sharable images mapped into local process space
>> and run just as if it had been in a locally loaded image? Does it make
>> any differnce from the outside? I mean, if you don't start looking at
>> actual physical addresses where the code is loaded into memory.
> 
> It was Craig that stated that it somehow acted differently.
> 
> I don't know why it would.
> 
> Maybe PCA does not distinguish between application shareable images
> and VMS shareable images and it don't want to measure VMS shareable
> images.
> 
> Maybe there is a different reason.
> 
> I have not used PCA since VAX.
> 
> Arne

Where the shareable image is mapped usually depends on if and how you
want to share code. Code of shareable images can be mapped into P0 but
also in S0/S1 or S2.

If a shareable image is installed with shared, resident code, it usually
was in S0/S1 (on x86 it usually is in S2). DECC$SHR is an example. I
don't know how PCA works, it may not work on shareable images where code
is shared.

Usually sharing of a shareable image can be avoided by telling the image
activator not to activate the installed image. This is done with a
logical name pointing to the image file, full file specification. A
DECC$SHR logical would point to SYS$SHARE:DECC$SHR.EXE;0 Then the CRTL
will be mapped to P0. This may be enough for PCA, but, as mentioned
above, I don't know.