| I'm still not sure I understand the question. Here's my interpretation
of what I think you want:
You get an OPCOM message from VAXB and it is sent to all systems in the
cluster as is typical of OPCOM messages. If any line of the OPCOM
message matches an event in the config database an event is triggered
on *all* systems in that cluster and you do not want this to happen.
If a message originates on VAXB you only want the event triggered on
VAXB. Correct?
If so then there is a somewhat rudimentary solution. You must use
either a timer on the filter(s) that might trap this event or you place
an event timer in the filter. Filters have two timers that may be used.
The filter timer says how many seconds between events must elapse
before the filter will be evaluated again. The event timer says how
many seconds between iterations of an event must occur before the event
will be dispatched to the action routine(s). This is the best you can
do prior to OpenVMS 7.0.
If your managed systems are running OpenVMS 7.0 there are two logicals
that can be defined as follows:
OPC$ALLOW_INBOUND
and
OPC$ALLOW_OUTBOUND
These logicals effect how inbound or outbound messages are handled. If
OPC$ALLOW_OUTBOUND is set to FALSE on all nodes in a cluster then you
have effectively disabled cluster-wide opcom messages. This is the
real solution to this very old problem.
Regs,
Dan
|