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 21592 articles. 0 followers. Post Follow

11 Replies
255 Views

Similar Articles

[PageSpeed] 8

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:

RE: Obsucure Inquier article about Intel mentions VMS (and not any other OS') other OS') other OS') other OS') other OS') other OS') other OS') other OS') other OS') other OS') other
> -----Original Message----- > From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]=20 > Sent: October 11, 2004 11:45 PM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: Obsucure Inquier article about Intel mentions=20 > VMS (and not any other OS') other OS') other OS') other OS')=20 > other OS') other OS') other OS') other OS') other OS') other=20 > OS') other OS') other OS') other OS') other OS') other OS') other=20 >=20 > "Main, Kerry" wrote: > > Course, there are many ways to offer differen...

RE: Obsucure Inquier article about Intel mentions VMS (and not any other OS') other OS') other OS') other OS') other OS') other OS') other OS') other OS') other OS')
> -----Original Message----- > From: Soterro [mailto:soterroatyahoocom@address.hp.com]=20 > Sent: October 11, 2004 9:43 AM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: Obsucure Inquier article about Intel mentions=20 > VMS (and not any other OS') other OS') other OS') other OS')=20 > other OS') other OS') other OS') other OS') other OS') >=20 > Main, Kerry wrote: > >>From: John Smith [mailto:a@nonymous.com]=20 > >>You aren't directly to blame for this and I know you'd like=20 > >>to keep your > &...

Making `logging.basicConfig` log to *both* `sys.stderr` and `sys.stdout`?
Hi, I use python oftentimes to write automation scripts on Linux servers. And there's a big pattern in my scripts: - I *always* use `logging` instead of `print` statements. - I *always* create two stream handlers. One for `sys.stdout` with level `INFO` and one for `sys.stderr` with level `WARN` Well, the levels may variate occasionally, but that's only the rare exception. The reason I do this is simple: Most automation tasks are run via cron. With this setup, I can redirect `stdout` to `/dev/null` and still receive e-mails if things go wrong. And having two handlers gives me more ...

SYS$SPECIFIC and SYS$COMMON not enough?
Basically, the idea is that stuff specific to a given node will be in its SYS$SPECIFIC directory and stuff common to all nodes (satellites or not) booting from the same system disk will be in SYS$COMMON. A good idea as far as it goes, but does it go far enough? In particular, there are two additional categories, which I'll give the obvious names SYS$CLUSTER and SYS$WORLD. SYS$CLUSTER would include stuff common to all nodes in a cluster, i.e. would differ from SYS$COMMON if there is more than one system disk in the cluster. The obvious place for this stuff is somewhere which is not ...

OS 9 startup in OS X
I have 2 iMacs, a G4 and a G5. The G5 does not have Classic installed but there is an icon for it in my system preferences. The G4 came with Classic installed but there is no icon for it in my system preferences. It is available as one of my startup disks. Whenever I restart, OS 9 tries to start up and I have to cancel the startup. How do I get the icon into my system preferences so that I can turn off the startup? In article <C19FA0F3.24C8A%linguine33@fuse.net>, Jules Freedman User <linguine33@fuse.net> wrote: > I have 2 iMacs, a G4 and a G5. The G5 does not have Classic ins...

Is compiler OS specific or Hardware specific....
hi, i have following doubts. is compiler OS specific or Hardware specific i.e processor specific.?? the confusion is because of the following (half ??)knowledge.. if the compiler is OS specific then one must know the internals of the OS!!! but since the OS like windows are proprietary and don't reveal any source code then how the compiler is designed for such an OS?? is it purely dependent on the processor architecture then??? also how the JVM for windows was made despite sun not knowing any of windows details?? or do OS vendors distribute kernel apis??? regds, yogesh ps. I post the same ...

RE: Obsucure Inquier article about Intel mentions VMS (and not any other OS') other OS') other OS')
> -----Original Message----- > From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]=20 > Sent: October 10, 2004 2:45 AM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: Obsucure Inquier article about Intel mentions=20 > VMS (and not any other OS') other OS') other OS') >=20 [snip..] >=20 > These days, the CIO reads trade mags on the commuter train=20 > and sees people > moving to windows or Linux and decides that his company must=20 > be ahead of the > race and hurry to migrate to this week's trendy product. >=20 >=20 > ITS ALL ABOU...

RE: Obsucure Inquier article about Intel mentions VMS (and not any other OS') other OS') other OS') #4
> -----Original Message----- > From: Larry Kilgallen [mailto:Kilgallen@SpamCop.net]=20 > Sent: October 11, 2004 5:33 AM > To: Info-VAX@Mvb.Saic.Com > Subject: RE: Obsucure Inquier article about Intel mentions=20 > VMS (and not any other OS') other OS') other OS') >=20 > In article=20 > <FD827B33AB0D9C4E92EACEEFEE2BA2FB45D86E@tayexc19.americas.cpqc > orp.net>, "Main, Kerry" <kerry.main@hp.com> writes: > >=20 > >> -----Original Message----- > >> From: Larry Kilgallen [mailto:Kilgallen@SpamCop.net]=3D20 > ...

RE: Obsucure Inquier article about Intel mentions VMS (and not any other OS') other OS') other OS') #2
> -----Original Message----- > From: John Smith [mailto:a@nonymous.com]=20 > Sent: October 10, 2004 6:18 PM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: Obsucure Inquier article about Intel mentions=20 > VMS (and not any other OS') other OS') other OS') >=20 [snip...] > How many 30'something CTO's even know what VMS is? How many=20 > of their system > architects or programmers? After the .crash era, there are likely very few CTO's left in their 30's. Those folks are more likely back in the trenches doing mid level mgmt jobs. Hey, I a...

RE: Obsucure Inquier article about Intel mentions VMS (and not any other OS') other OS') other OS') #3
> -----Original Message----- > From: Larry Kilgallen [mailto:Kilgallen@SpamCop.net]=20 > Sent: October 10, 2004 10:52 PM > To: Info-VAX@Mvb.Saic.Com > Subject: RE: Obsucure Inquier article about Intel mentions=20 > VMS (and not any other OS') other OS') other OS') >=20 > In article=20 > <FD827B33AB0D9C4E92EACEEFEE2BA2FB45D86D@tayexc19.americas.cpqc > orp.net>, "Main, Kerry" <kerry.main@hp.com> writes: >=20 > > for that matter. However, I know of two major Customers=20 > that wanted to > > convert OpenVMS applica...

Re: SYS$SPECIFIC and SYS$COMMON not enough?
> >What are some real-world examples of stuff which is common to all nodes > >which boot from a common system disk, but not common to all nodes in a > >cluster, even in a share-as-much-as-possible cluster? > > One use of a cluster is testing new system SW. You can make a copy of your > main system disk and upgrade the software there (say, a VMS patch). Then > boot one system using that disk and see how it works, while the rest of the > cluster does your production work using the old system without the upgrade. > In that case, any files affected by the ...

Re: SYS$SPECIFIC and SYS$COMMON not enough? #2
> How weird - we did this as a different excercise to do upgrades off > line on the read only stuff, and swap it back in quickly. We also have > a third party product root to keep our own/third party stuff out of > SYS$SYSDEVICE:[VMS$COMMON...] tree, like a "/usr/local...". > > H sh lo sys$sysroot > "SYS$SYSROOT" = "$9$DKA0:[SYS0.]" (LNM$SYSTEM_TABLE) > = "SYS$COMMON:" > 1 "SYS$COMMON" = "CLU$COMMON:" (LNM$SYSTEM_TABLE) > = "VMS$COMMON:" > = "OUR$COMMON:&...

Logging Who Logs In
How can I keep track of who logs into my ASE (15.0.2)? Thanks, Steve -- Steven J. Backus Computer Specialist University of Utah E-Mail: steven.backus@utah.edu Genetic Epidemiology Alternate: backus@math.utah.edu 391 Chipeta Way -- Suite D Office: 801.587.9308 Salt Lake City, UT 84108-1266 http://www.math.utah.edu/~backus Hello, Enable auditing: http://infocenter.sybase.com/help/topic/com.sybase.help.ase_15.0.sag1/html/sag1/sag1831.htm Thanks, Neal On Dec 3, 9:04=A0pm, bac...@ep...

SYS$STARTUP:MMOV$STARTUP.COM -- lacks something (priority)
And while I'm complaining about SYS$STARTUP:MMOV$SHUTDOWN.COM, I recently (at long last) figured out why I've been getting such choppy MPEG playback after system startup until I manually restart the MMOV$SERVER process. In SYS$STARTUP:MMOV$STARTUP.COM, the "RUN /DETACHED" command lacks a "/PRIORITY" qualifier, so if it's run from a typical batch queue (as it was on my system), the MMOV$SERVER process inherits a reduced process priority, resulting in poor performance. (And on an AlpSta 200 4/233, it needs all the performance advantages it can scrape toget...

Web resources about - SYS$SPECIFIC:[SYSEXE]STARTUP.LOG - comp.os.vms

Resources last updated: 2/4/2016 6:35:44 AM