[Info-vax] SYS$SPECIFIC:[SYSEXE]STARTUP.LOG

[Paul Sture]

In article <00ACE1CC.FB1BDF28 at SendSpamHere.ORG>,
 VAXman-  @SendSpamHere.ORG wrote:

> In article <ke9f6j$uq3$1 at online.de>, helbig at astro.multiCLOTHESvax.de (Phillip 
> Helbig---undress to reply) writes:
> >In article <00ACE1C4.F3583332 at SendSpamHere.ORG>, VAXman-  @SendSpamHere.ORG 
> >writes:
> >> In article <ke9dh9$tkb$1 at online.de>, helbig at astro.multiCLOTHESvax.de 
> >> (Phillip Helbig---undress to reply) writes:
> >> >What determines whether SYS$SPECIFIC:[SYSEXE]STARTUP.LOG is written 
> >> >during startup?
> >> >
> >> 
> >> $ MCR SYSGEN
> >> SYSGEN> SET STARTUP_P2 "V"
> >> SYSGEN> WRITE CURRENT
> >> SYSGEN> EXIT
> >> -- 
> >> VAXman- A Bored Certified VMS Kernel Mode Hacker    
> >> VAXman(at)TMESIS(dot)ORG
> >> 
> >> Well I speak to machines with the voice of humanity.
> >
> >
> >I noticed that this is the case on the satellite discussed in another 
> >thread, but not on any of the other machines.  I don't recall ever 
> >setting it; maybe my own memory has a parity error.
> 
> I usually set mine to "VDC" and leave it.  My SYSTARTUP_VMS.COM has a purge
> and rename to ;1 of SYS$SPECIFIC:[SYSEXE]STARTUP.LOG.  Set it and forget it
> unless it's handy/needed.

Ditto with the setting of "VDC" but I purge to 5 versions in a separate 
daily maintenance job so that in the event of finger trouble when 
modifying startup procedures, or hardware errors causing repeated 
starts, I have more diagnostic information to go at.

-- 
Paul Sture