Is it true that OPERATOR.LOG contains all OPCOM messages, even those 
generated before it was opened?

Phillip Helbig---remove CLOTHES to reply wrote:
> 
> Is it true that OPERATOR.LOG contains all OPCOM messages, even those
> generated before it was opened?

no.

look in sylogicals.com for OPC , there is a fair amount of doc on how
you can customise what goes into operator.log and on terminals.

also, some non-opcom messages do not make it to operator.log (page file
badly fragmented, and some of the cluster transition messages.

In article <dsn1oo$iti$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:
>Is it true that OPERATOR.LOG contains all OPCOM messages, even those 
>generated before it was opened?

1) No
2) OPERATOR.LOG contains all message from all enabled classes destined
for the logfile. See the OPC$LOGFILE_CLASSES and OPC$LOGFILE_ENABLE logicals
3) OPERATOR.LOG is created on boot and closed on shutdown
(and can be controlled also with REPLY/[NO]LOG by an enabled operator)
It will not be appended automatically. You could $ APPEND OPERATOR.LOG;-1
OPERATOR.SAVE_ME at every boot to get one big logfile (across boots).

-- 
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail  peter@langstoeger.at
A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist

In article <43ef4275$1@news.langstoeger.at>, peter@langstoeger.at (Peter
'EPLAN' LANGSTOEGER) writes: 

> 3) OPERATOR.LOG is created on boot 

When, exactly?

In article <43EF179F.52D21B36@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:
> Phillip Helbig---remove CLOTHES to reply wrote:
>> 
>> Is it true that OPERATOR.LOG contains all OPCOM messages, even those
>> generated before it was opened?

> also, some non-opcom messages do not make it to operator.log (page file
> badly fragmented, and some of the cluster transition messages.

But he specifically asked about OPCOM messages.

In article <dsnfpk$hg1$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:
>In article <43ef4275$1@news.langstoeger.at>, peter@langstoeger.at (Peter
>'EPLAN' LANGSTOEGER) writes: 
>
>> 3) OPERATOR.LOG is created on boot 
>
>When, exactly?

By running SYS$STARTUP:VMS$CONFIG-050_OPCOM.COM in the SYSMAN CONFIG phase.

$ TYPE SYS$STARTUP:VMS$PHASES.DAT	!list all SYSMAN startup phases
$ MCR SYSMAN				!list all SYSMAN startup procedures
SYSMAN> STARTUP SET DATABASE STARTUP$STARTUP_VMS
SYSMAN> STARTUP SHOW FILE/FULL
SYSMAN> STARTUP SET DATABASE STARTUP$STARTUP_LAYERED
SYSMAN> STARTUP SHOW FILE/FULL

btw: Don't forget to check SYS$SYSTEM:STARTUP.COM

In my case, boottime is about 39sec earlier than creation time of the OP*.LOG

-- 
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail  peter@langstoeger.at
A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist

In article <43ef709a$1@news.langstoeger.at>, peter@langstoeger.at (Peter
'EPLAN' LANGSTOEGER) writes: 

> In article <dsnfpk$hg1$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:
> >In article <43ef4275$1@news.langstoeger.at>, peter@langstoeger.at (Peter
> >'EPLAN' LANGSTOEGER) writes: 
> >
> >> 3) OPERATOR.LOG is created on boot 
> >
> >When, exactly?
> 
> By running SYS$STARTUP:VMS$CONFIG-050_OPCOM.COM in the SYSMAN CONFIG phase.
> 
> $ TYPE SYS$STARTUP:VMS$PHASES.DAT	!list all SYSMAN startup phases
> $ MCR SYSMAN				!list all SYSMAN startup procedures
> SYSMAN> STARTUP SET DATABASE STARTUP$STARTUP_VMS
> SYSMAN> STARTUP SHOW FILE/FULL
> SYSMAN> STARTUP SET DATABASE STARTUP$STARTUP_LAYERED
> SYSMAN> STARTUP SHOW FILE/FULL
> 
> btw: Don't forget to check SYS$SYSTEM:STARTUP.COM
> 
> In my case, boottime is about 39sec earlier than creation time of the OP*.LOG

I'm defining the name of the log file via SYLOGICALS.COM.  Is this 
before or after the operator log is created?  If after, does a new one 
get opened at the defined location?  If before, can I count on it being 
always before?

In article <dsnvfe$qpk$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:
>I'm defining the name of the log file via SYLOGICALS.COM.  Is this 
>before or after the operator log is created?  If after, does a new one 
>get opened at the defined location?  If before, can I count on it being 
>always before?

How about checking yourself ?
SYLOGICALS is run in the DEVICES phase (SYS$STARTUP:VMS$DEVICE_STARTUP.COM)
which is 2 phases before the CONFIG phase.

$ TYPE SYS$STARTUP:VMS$PHASES.DAT
INITIAL
DEVICES
PRECONFIG
CONFIG
BASEENVIRON
LPBEGIN
LPMAIN
LPBETA
END

Define STARTUP_P2 as "DC" and see in your SYS$SYSTEM:STARTUP.LOG...

-- 
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail  peter@langstoeger.at
A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist

Phillip Helbig---remove CLOTHES to reply wrote:
> > 3) OPERATOR.LOG is created on boot
> 
> When, exactly?

There is a message on opa0 when opcom is created. It is done after
sylogicals.com has been executed (since it looks at logicals defined in
it), but before systartup_vms.com has been called.