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

[Dave Froble]

On 10/16/2020 4:56 PM, Stephen Hoffman wrote:
> On 2020-10-16 19:12:57 +0000, Dave Froble said:
>
>> 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?
>
> Apps requiring startups are a subset of apps installed, and something
> any new package manager will be expected to provide.

Well, I don't have any idea what a package manager is.  Maybe it's 
semantics?  My apps do have background functions that are normally 
started shortly after VMS starts, and that is triggered by the VMS startup.

> Well more than zero and somewhat less than all apps installed will have
> an associated startup procedure, and various of those will also have a
> shutdown procedure.

Yep, startup and shutdown, and messaging to manage the detached 
functions.  Been doing that for over 30 years.  Got to wonder why it's 
an issue now.

> Efforts to extend both VMSINSTAL and PCSI to transparently manage app
> startups failed.

Would not want anything not part of the apps to have anything to do with 
the apps.

> I doubt that any package manager design will involve automated editing
> within a DCL command procedure that is also human-edited.

Would not do such.  Too much hands-on.  Much better to have messaging to 
manage things.


-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486