topic Re: An illegal operator request was made in Operating System - OpenVMS

An illegal operator request was made

Dolezel Vaclav — Thu, 06 Nov 2008 07:53:33 GMT

Hello.

I have a cluster with 3 nodes. On first node command REPLY/ENABLE is making this result "An illegal operator request was made". On the other nodes is working normally. I cannot find the problem. Please help. Thanks in advance.

Re: An illegal operator request was made

Jan van den Ende — Thu, 06 Nov 2008 08:00:12 GMT

Vaclav,

Mostly this error is issued when the requestor does NOT have OPER priv active.

Could it be that on the first not you NOT have it, while on the others you DO?

Proost.

Have one on me.

jpe

Re: An illegal operator request was made

Dolezel Vaclav — Thu, 06 Nov 2008 08:09:48 GMT

I'm using same account which have OPER privilige.

Re: An illegal operator request was made

Accullise — Thu, 06 Nov 2008 08:18:47 GMT

Hi vaclav,

Generally these errors are coming when you have already enable the opcom.

first try with reply/disable and then try reply/enable.

regds,
Accullise

Re: An illegal operator request was made

Dolezel Vaclav — Thu, 06 Nov 2008 08:22:06 GMT

It's the same.

CUW1:SMSC> reply/ena
%%%%%%%%%%% OPCOM 5-NOV-2008 23:16:21.47 %%%%%%%%%%%
An illegal operator request was made

CUW1:SMSC> reply/disa
%%%%%%%%%%% OPCOM 5-NOV-2008 23:16:22.15 %%%%%%%%%%%
An illegal operator request was made

Re: An illegal operator request was made

Accullise — Thu, 06 Nov 2008 08:29:54 GMT

when you have created the operator.log file....

what is the size of the log file...

could you able to put the command reply/log....

when you put reply/log the same error is coming or not?

Re: An illegal operator request was made

Robert Gezelter — Thu, 06 Nov 2008 08:48:08 GMT

Doelzel,

Please show the output from SHOW PROCESS/PRIVILEGE on the node generating the error message.

It is possible that while the account is authorized for OPER, it is not enabled by default.

- Bob Gezelter, http://www.rlgsc.com

Re: An illegal operator request was made

Jan van den Ende — Thu, 06 Nov 2008 09:09:38 GMT

Vaclav,

if you really have the OPER priv active, then matbe the OPCOM process is not running?

$ SHOW SYSTEM/PROC=OPCOM

If not, then as user SYSTEM (batch job?) execute

$ @SYS$SYSTEM:STARTUP OPCOM

Proost.

Have one on me.

jpe

Re: An illegal operator request was made

Dolezel Vaclav — Thu, 06 Nov 2008 09:16:37 GMT

Process have OPER privilege.

REPLY/LOG have same result.

Re: An illegal operator request was made

Dolezel Vaclav — Thu, 06 Nov 2008 09:17:51 GMT

OPCOM process is running under SYSTEM account.

Re: An illegal operator request was made

Accullise — Thu, 06 Nov 2008 09:46:18 GMT

login from system account...
then check opcom is running or not..
(show system/proc=opcom)
if it is available,stop that process ...
(stop/id=xxxxxxx)
and restart the opcom process from system account with the following command...
@sys$system:startup opcom

and then check have got any messages in the operator.log file and then

reply/ena
reply/log
reply/dis

and check whether new operator.log file created or not and what is the size of the last operator.log file.

regds,
Accullise

Re: An illegal operator request was made

Willem Grooters — Thu, 06 Nov 2008 10:15:10 GMT

Stupid, perhaps, but what is the output of

$ show sym rep*

I've run into unexpected results due to the fact that symbols overrules standard commands...

Re: An illegal operator request was made

Dolezel Vaclav — Thu, 06 Nov 2008 10:18:41 GMT

Any REP* symbol defined.

Re: An illegal operator request was made

Dolezel Vaclav — Thu, 06 Nov 2008 15:31:46 GMT

After restarting OPCOM problem is gone. thanks