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

johnwallace4 at yahoo.co.uk johnwallace4 at yahoo.co.uk
Thu Oct 15 11:42:18 EDT 2020


On Thursday, 15 October 2020 16:26:26 UTC+1, 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.
> 
> -- 
> Marc Van Dyck

Same here too, for many happy years on many systems.

But I guess some folk thrive on unnecessary complexity - it 
seems to have become the way of the IT department in many places.




More information about the Info-vax mailing list