[Info-vax] Logging systartup_vms.com progress to operator.log VMS 7.3-2

[Stephen Hoffman]

On 2020-10-19 18:01:55 +0000, Dave Froble said:

> On 10/19/2020 8:31 AM, Simon Clubley wrote:
>> On 2020-10-16, Dave Froble <davef at tsoft-inc.com> wrote:
>>> On 10/16/2020 8:45 AM, Simon Clubley wrote:
>>>> 
>>>> That's the whole point of a package manager so that you don't have to 
>>>> code the same checks over and over again in every application you write.
>>>> 
>>>> List what you need in your install script and let the package manager 
>>>> take care of the details.
>>>> 
>>>> And don't forget that dependency requirements can be nested, which a 
>>>> package manager takes care of for you.
>>> 
>>> Just to clear up my confusion, are we discussing installing software, 
>>> or, starting VMS?
>> 
>> They are both part of the same thing. Think about it.
> 
> It hurts my brain to attempt to think about that.  The way I see 
> things, those are two very different things.
> 
> Installation: loading software onto system and preparing it for 
> operations.  A one time operation.
> 
> System startup: uh, like it reads, starting VMS.  Can happen quite often.

The difference here is whether the inclusion of the startup procedure 
for the app being installed is performed manually based on reading 
app-provided documentation, or is automated.

The automated approach involves a request by the app developer creating 
the installer package—invoking a PCSI directive or VMSINSTAL callback, 
in the case of OpenVMS—in conjunction with the developers of the 
package manager itself.

The automated inclusion of app-specific startup scripts into the system 
startup is common on other platforms.

And no, the automated scripts aren't appended onto a human-edited file. 
Other means are used to locate and sequence and invoke the startup 
scripts.


-- 
Pure Personal Opinion | HoffmanLabs LLC