Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!styx!ames!ucbcad!ucbvax!JPL-VLSI.ARPA!xrjjm%firas.span
From: xrjjm%firas.span@JPL-VLSI.ARPA
Newsgroups: comp.os.vms
Subject: Inhibiting Security Messages
Message-ID: <870428081657.026@Jpl-VLSI.ARPA>
Date: Tue, 28-Apr-87 11:16:56 EDT
Article-I.D.: Jpl-VLSI.870428081657.026
Posted: Tue Apr 28 11:16:56 1987
Date-Received: Sat, 2-May-87 04:50:18 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 29

Comment:   Begin User Supplied Mail Headers.
*Site:     NASA Goddard Space Flight Center - Greenbelt, Maryland, USA.
*Position: 76 Deg. 52' 28.5" West, 38 Deg. 59' 59.8" North.
*From:     John J. McMahon, Systems Programmer, STX - ST Systems Corporation.
*Project:  COBE Science Data Room (CSDR), Code 401.1
*Reply-To: (Arpa-Internet)       XRJJM%CSDR.SPAN@JPL-VLSI.ARPA
*Reply-To: (Bitnet)              ZMJJM@SCFVM
*Reply-To: (Span/Physnet/Hepnet) 6173::XRJJM = CSDR::XRJJM (Node 6.29)
*Reply-To: (TEXnet)              UTADNX::UTSPAN::CSDR::XRJJM

>	There were some messages earlier that pointed out that you
>	can disable some OPCOM messages on the console by using
>	commands
> 
>		$ DEFINE/USER SYS$COMMAND OPA0
>		$ REPLY/DISABLE=whatever
> 
>	This also appears to prevent the messages from appearing
>	in the OPERATOR.LOG file.

We use this technique to prevent SECURITY messages from showing up on
OPAO:, I tested it and found that it doesn't inhibit the entries being
put in OPERATOR.LOG

A local bug perhaps ?
^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
John J. McMahon (Fast-Eddie)                     
Disclaimer: Views expressed in this letter are my own, 
            and are not meant to represent the views of my employers.