SYS$SPECIFIC:[SYSEXE]STARTUP.LOG

What determines whether SYS$SPECIFIC:[SYSEXE]STARTUP.LOG is written 
during startup?

0
helbig (5064)
1/29/2013 9:04:41 PM
comp.os.vms 21332 articles. 0 followers. Post Follow

11 Replies
151 Views

Similar Articles

[PageSpeed] 45
In article <ke9dh9$tkb$1@online.de>, helbig@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.
0
VAXman
1/29/2013 9:20:00 PM
In article <00ACE1C4.F3583332@SendSpamHere.ORG>, VAXman-  @SendSpamHere.ORG writes:
> In article <ke9dh9$tkb$1@online.de>, helbig@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.

0
helbig (5064)
1/29/2013 9:33:07 PM
In article <ke9f6j$uq3$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply) writes:
>In article <00ACE1C4.F3583332@SendSpamHere.ORG>, VAXman-  @SendSpamHere.ORG writes:
>> In article <ke9dh9$tkb$1@online.de>, helbig@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.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.
0
VAXman
1/29/2013 10:17:29 PM
On Tuesday, January 29, 2013 10:20:00 PM UTC+1, VAXm...@SendSpamHere.ORG wrote:
> In article <ke9dh9$tkb$1@online.de>, helbig@...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.

From SYS$SYSTEM:STARTUP.COM :

$if f$locate("V",p2) .nes. f$length(p2) then stdrv$verify = stdrv$true
$if f$locate("D",p2) .nes. f$length(p2) then stdrv$log = stdrv$true
$if f$locate("C",p2) .nes. f$length(p2) then stdrv$verbose = stdrv$true
$if f$locate("P",p2) .nes. f$length(p2) then stdrv$comp_verify = stdrv$true

So if you include "D" in STARTUP_P2 the startup log file is created. What goes into the log file is determined by the other three options. "V" turns on verification of all startup command procedures and generates a lot of text.

I normally use "DC". That generates a small log file with all relevant (to me)information.

HTH,

Bart
0
Bart.Zorn2 (178)
1/30/2013 6:14:27 AM
On 29 jan, 22:33, hel...@astro.multiCLOTHESvax.de (Phillip Helbig---
undress to reply) wrote:

> I noticed that this is the case on the satellite discussed in another
> thread, but not on any of the other machines. =A0I don't recall ever
> setting it; maybe my own memory has a parity error.

You might have enabled this with the SYSMAN utility:

SYSMAN> startup set options/output=3Dfile

Oswald
0
1/30/2013 8:51:18 AM
In article 
<5d5bdeb1-85f8-44e5-a033-0cfbca1c6a2f@h2g2000yqa.googlegroups.com>,
 Oswald <oswald.knoppers@gmail.com> wrote:

> On 29 jan, 22:33, hel...@astro.multiCLOTHESvax.de (Phillip Helbig---
> undress to reply) wrote:
> 
> > 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.
> 
> You might have enabled this with the SYSMAN utility:
> 
> SYSMAN> startup set options/output=file

That won't modify MODPARAMS.DAT so you will lose the setting on your 
next AUTOGEN.

-- 
Paul Sture
0
nospam9740 (2260)
1/30/2013 11:30:28 AM
In article <00ACE1CC.FB1BDF28@SendSpamHere.ORG>,
 VAXman-  @SendSpamHere.ORG wrote:

> In article <ke9f6j$uq3$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip 
> Helbig---undress to reply) writes:
> >In article <00ACE1C4.F3583332@SendSpamHere.ORG>, VAXman-  @SendSpamHere.ORG 
> >writes:
> >> In article <ke9dh9$tkb$1@online.de>, helbig@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
0
nospam9740 (2260)
1/30/2013 11:35:16 AM
On Tuesday, January 29, 2013 4:04:41 PM UTC-5, Phillip Helbig---undress to =
reply wrote:
> What determines whether SYS$SPECIFIC:[SYSEXE]STARTUP.LOG is written=20
>=20
> during startup?

Phillip,

My preference on running systems is to use SYSMAN for short-term changes. F=
or permanent changes (e.g., I generally want unattended machines to log the=
 startup process to a file, rather than to an unwatched screen), I would pu=
t the change into MODPARAMS.DAT to ensure that the "policy" change propagat=
es through future operation of AUTOGEN.

Of course, if I am building/maintaining an OpenVMS Cluster, I prefer to mai=
ntain site/cluster-specific underlying MODPARAMS.DAT files as an underlying=
 base for site/cluster-generic parameter settings. I discussed this use of =
AGEN$INCLUDE in my 2011 OpenVMS Bootcamp presentation "Using OpenVMS Techno=
logies to Build an Agile Computing Base" (slides/audio available at: http:/=
/www.rlgsc.com/openvms-bootcamp/2011/agile-openvms.html)

- Bob Gezelter, http://www.rlgsc.com
0
gezelter (551)
1/30/2013 5:01:27 PM
In article
<5d5bdeb1-85f8-44e5-a033-0cfbca1c6a2f@h2g2000yqa.googlegroups.com>,
Oswald <oswald.knoppers@gmail.com> writes: 

> On 29 jan, 22:33, hel...@astro.multiCLOTHESvax.de (Phillip Helbig---
> undress to reply) wrote:
> 
> > I noticed that this is the case on the satellite discussed in another
> > thread, but not on any of the other machines. =A0I don't recall ever
> > setting it; maybe my own memory has a parity error.
> 
> You might have enabled this with the SYSMAN utility:
> 
> SYSMAN> startup set options/output=file

I don't think I've ever used SYSMAN> Startup.  :-)

0
helbig (5064)
1/30/2013 7:53:25 PM
In article <4a66abd2-3217-4cc0-a38b-753410c41b96@googlegroups.com>, Bart Zorn <bart.zorn@gmail.com> writes:
>On Tuesday, January 29, 2013 10:20:00 PM UTC+1, VAXm...@SendSpamHere.ORG wrote:
>> In article <ke9dh9$tkb$1@online.de>, helbig@...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.
>
>From SYS$SYSTEM:STARTUP.COM :
>
>$if f$locate("V",p2) .nes. f$length(p2) then stdrv$verify = stdrv$true
>$if f$locate("D",p2) .nes. f$length(p2) then stdrv$log = stdrv$true
>$if f$locate("C",p2) .nes. f$length(p2) then stdrv$verbose = stdrv$true
>$if f$locate("P",p2) .nes. f$length(p2) then stdrv$comp_verify = stdrv$true
>
>So if you include "D" in STARTUP_P2 the startup log file is created. What goes into the log file is determined by the other three options. "V" turns on verification of all startup command procedures and generates a lot of text.
>
>I normally use "DC". That generates a small log file with all relevant (to me)information.

Yeah, I mentioned that I alwasy set mine to "VDC".  I couldn't remember
which enabled the actual log.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.
0
VAXman
1/30/2013 8:14:04 PM
In article <kebtnl$u94$1@online.de>,
 helbig@astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply) 
 wrote:

> In article
> <5d5bdeb1-85f8-44e5-a033-0cfbca1c6a2f@h2g2000yqa.googlegroups.com>,
> Oswald <oswald.knoppers@gmail.com> writes: 
> 
> > On 29 jan, 22:33, hel...@astro.multiCLOTHESvax.de (Phillip Helbig---
> > undress to reply) wrote:
> > 
> > > I noticed that this is the case on the satellite discussed in another
> > > thread, but not on any of the other machines. =A0I don't recall ever
> > > setting it; maybe my own memory has a parity error.
> > 
> > You might have enabled this with the SYSMAN utility:
> > 
> > SYSMAN> startup set options/output=file
> 
> I don't think I've ever used SYSMAN> Startup.  :-)

The SYSMAN STARTUP commands are not the most intuitive...

-- 
Paul Sture
0
nospam9740 (2260)
1/31/2013 12:12:47 PM
Reply:
Similar Artilces: