🚀 go-pugleaf

sdroppers@pbs.org writes:

>In article <1992Jul20.135138.938@beckman.com>, dsroberts@beckman.com writes:> cluster.  He did not use the STARTUP$STARTUP_VMS and STARTUP$STARTUP_LAYERED
>> ...stuff removed...
>> In any case, perhaps some of you would like to share how your startup is
>> configured so perhaps I can glean some improvements that would apply to us.
>> 
>We have had very good results starting the batch queues and then sending
>jobs off in the batch queues.  We cut our reboot time from 45 minutes to about
>15 minutes this way.  We abandoned the DEC supplied startup since we could not
>specify the batch queue to start jobs in.
>
>By using batch queues we can also specify the exact order items are started.

Interestingly enough, I had the opportunity to view the startup procedures of
a large and strategically important Digital internal VAXcluster system.
I didn't bother to check if they were using the STARTUP$STARTUP_LAYERED data
file scheme, but they had a *lot* of startup procedures submitted to batch
queues.  Almost nothing was executed during SYSTARTUP_V5.  I counted at least
75 startup procedures of various products, etc, all launched in batch.  I
presume they did/do not use the STARTUP_LAYERED scheme.  I have noticed that
certain Digital "consultants" seem to be favoring this however.

I personally don't have enough products to even bother investigating this
bit of VMS "boot trivia", but I would favor the batch method if I did.
-- 
richard@npri6.npri.com  <Richard Head>
I've fallen and I can't reach my beer!