topic Operator.log in Operating System - OpenVMS

Operator.log

Aureo de Souza Lima — Thu, 15 Jul 2004 15:03:54 GMT

In boot of my Alpha-Openvms system, the operator.log is not started
automatically. I added to the commands

reply/enable
reply/log
reply/disable

in syslogicals.com but I did not get resulted.

Please help-me and sorry my poor English. :)

Re: Operator.log

labadie_1 — Thu, 15 Jul 2004 15:19:50 GMT

It would help to know your Vms version.

If you do interactively
$ reply/enable
$ reply/log

It will start tyhe operator.log

If you want to do it in batch, or in sys$startup:sylogicals.com (no syslogicals.com)
you need to do something like

$ DEFINE SYS$COMMAND _OPA0:
$ REPLY/ENABLE
$ REPLY/LOG

Re: Operator.log

John Gillings — Thu, 15 Jul 2004 16:43:03 GMT

Aureo,

As Gerard has pointed out, many REPLY commands are intended to be executed interactively, and will not work unless SYS$COMMAND points to a real terminal device.

It is not necessary, or advisable to have REPLY commands in SYLOGICALS.COM. OPCOM should start automatically (but note - not until AFTER SYLOGICALS.COM has completed). The "correct" way to control OPCOM is to define the appropriate OPC$ logical names in SYLOGICALS.COM.

For example:

$ DEFINE/SYSTEM/EXEC OPC$LOGFILE_ENABLE "TRUE"
$ DEFINE/SYSTEM/EXEC OPC$LOGFILE_NAME "LOGS:OPERATOR.LOG"

etc... You only need to define these logical names if you want different OPCOM behaviour from default. See the comments in SYLOGICALS.TEMPLATE for more detail.

Re: Operator.log

Mobeen_1 — Fri, 16 Jul 2004 06:48:33 GMT

Aureo,
I totally agree with labadie and john. Those are the only 2 methods i am aware of.

Normally if you would like to do it interactively then the way is to use reply/log

regards
Mobeen

Re: Operator.log

Uwe Zessin — Fri, 16 Jul 2004 07:00:02 GMT

The third method is to use the system service (I have forgotten the name - SYS$SNDOPR or so). I would not try this unless I was eager to fight with the data structures - it is really a masterpiece ;-)

Re: Operator.log

Galen Tackett — Fri, 16 Jul 2004 07:58:45 GMT

Aureo,

There was some recent discussion in comp.os.vms about problems with the operator log file not being created and about OPC$LOGFILE_ENABLE being ignored.

You might want to check out that discussion by opening this url:

http://tinyurl.com/67vos

I hope this helps you.

Galen

Re: Operator.log

Aureo de Souza Lima — Fri, 16 Jul 2004 12:12:44 GMT

Thanks for all, friends!

I don't have logical names in the system that has relation with
operator.log, except what start the OPCOM.

I go to change "replys" for the logical names in sylogicals.com and to
program one boot in the next week.

Re: Operator.log

Martin P.J. Zinser — Sat, 17 Jul 2004 20:14:11 GMT

Hello Aureo,

please try to explain your problem a bit better.

From your posts I see two possible problems:

a.) The OPCOM process does not get started at all, i.e. no Opcom messages are generated and written to the operator.log file.

To check if the opcom process is executing do a

$ sh sys/proc=*opc*

If the process is running you should see something like this

$ sh sys/proc=*opc*
OpenVMS V7.3-2 on node KORONA 17-JUL-2004 20:10:13.01 Uptime 1 12:08:41
Pid Process Name State Pri I/O CPU Page flts Pages
00000409 OPCOM HIB 9 1062 0 00:00:00.60 93 46

2.) Opcom is running and you do want to get opcom messages as a particular user and or
on the operator console.

So, which of these is your problem?

Greetings, Martin