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

[Dave Froble]

On 10/15/2020 11:26 AM, Marc Van Dyck wrote:
> Dave Froble formulated on Wednesday :
>>>
>>
>> I'll just mention my practice.
>>
>> SYSTARTUP_VMS.COM does the minimum necessary, then, one or more batch
>> jobs are run to do the rest of the startup.  Network startup and such.
>> Additional queues.  Terminal setup.  Application startup(s).  Most
>> things that are not required in SYSTARTUP_VMS.COM.
>>
>> Of course, the batch jobs produce logs.
>
> Same here.
>
> In addition to producing logs, it also runs faster because running in
> processes that can have much larger quota than those of the startup
> process.
>
> It also frees up the console faster, allowing sysadmins to login while
> startup batch jobs are still executing, which can be useful for
> troubleshooting. Of course SET LOGIN/INTER=xxx is only executed after
> all startup jobs are finished, so normal users can't login before the
> startup is complete.
>
> The startup jobs execute in a dedicated queue with job limit=1.
>

All of that.  However, I allowed logins as soon as possible.  Some 
functions didn't need the background processes, and if they did, they 
checked first.  After the death of attached terminals, didn't matter, 
users weren't getting on until the network was running.

-- 
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