[Info-vax] Logging image activations

[Jan-Erik Söderholm]

P. Sture wrote:
> In article <KJeHm.12506$U5.185708 at newsb.telia.net>,
>  Jan-Erik Söderholm <jan-erik.soderholm at telia.com> wrote:
> 
>> P. Sture wrote:
>>> In article <NGQFm.12425$U5.180157 at newsb.telia.net>,
>>>  Jan-Erik Söderholm <jan-erik.soderholm at telia.com> wrote:
>>>
>>> I generally recommend that SET ACCOUNTING/ENABLE=IMAGE is reserved for 
>>> diagnostic purposes only.
>>>
>>> For example, DCL SET commands invoke SET.EXE and these get logged in the 
>>> accounting file, so as you can imagine image accounting fills the disk 
>>> up pretty quickly. A DCL procedure doing repetitive processing can 
>>> easily run up tens of thousands of image accounting records.
>>>
>>> Unless you have your accounting files on a different disk from the audit 
>>> files, you are risking grinding your system to a halt.
>>>
>> Yes, absolutely. That is the main drawback of genarally
>> enableling image accounting. I will probaby do some test
>> using the porposed "$ INSTALL CREATE imagename /ACCOUNTING"
>> by Jeremy Begg. I guess that that will introduce some (one?)
>> extra steps (INST REPL ?) when copying a new image from the
>> development/test system. But besides of that, it seems as a
>> nice addition.
>>
>> One other issue is that some of the "images" I'm interested in
>> are build as a large EXE with different entry points, and if
>> possible I'd be interested in which of the entry points gets called.
>> They are setup with the name of the EXE and the entry point
>> in the menu system used. But that is maybe a little harder to do
>> without some loogging in the code itself (I guess).
>>
> 
> Do you have the sources to the menu system?
> 

I do not think so, have to search the system. I seem to remember
that it was written and sold by some Swedish company, and it
is (was) called "Menu/1". It's quite nice, if you need a VT-based
menu system...