Notify
Notify=All
Notify=Noall
Notify=operator-classes
Nonotify
Notifies the specified system operator or operators when a
stall process exceeds the specified alarm interval by issuing
a broadcast message and ringing a bell at the terminal receiving
the message.
The valid operator classes are: CENTRAL, CLUSTER, DISKS, OPCOM,
SECURITY, and OPER1 through OPER12.
The various forms of the Notify qualifier have the following
effects:
o If you specify the Notify qualifier without the operator-
classes parameter, the CENTRAL and CLUSTER operators are
notified by default.
o If you specify the Nonotify or Notify=Noall qualifiers,
operator notification is disabled.
o If you specify the Notify=All qualifier, all operator classes
are enabled.
o If you specify the Notify=operator-classes qualifier, the
specified classes are enabled. (If you specify more than one
operator class, enclose the list in parentheses and separate
each class name with a comma.)
For example, issuing the RMU Show Statistics command with the
Notify=(OPER1, OPER2) qualifier sends a notification message
to system operator classes OPER1 and OPER2 if the Alarm
threshold is exceeded while monitoring the Stall Messages
screen.
o When the Notify=OPCOM qualifier is specified with the RMU
Show Statistics command along with the Alarm and Cluster
qualifiers, Oracle RMU generates an OPCOM message and delivers
it to the OPCOM class associated with the Notify qualifier.
This message alerts the operator to the fact that the process
has stalled for more than n seconds, where n is the value
assigned to the Alarm qualifier. The process that has stalled
may be on any node that is included in the node name list
assigned to the Cluster qualifier.
The specified system operator(s) are notified only when the alarm
threshold is first exceeded. For instance, if three processes
exceed the alarm threshold, the specified operator(s) are
notified only once. If another process subsequently exceeds the
alarm threshold while the other processes are still displayed,
the specified system operator(s) are not notified.
However, if the longest-duration stall is resolved and a new
process then becomes the newest stall to exceed the alarm
threshold, then the specified system operator(s) will be notified
of the new process.
To receive operator notification messages, the following three
OpenVMS DCL commands must be issued:
1. $ SET TERM /BROADCAST
2. $ SET BROADCAST=OPCOM
3. $ REPLY /ENABLE=(operator-classes)
The operator-classes specified in the REPLY /ENABLE command must
match those specified in the Notify qualifier to the RMU Show
Statistics command.
The operator notification message will appear similar to the
following sample message:
%%%%%%%%%%% OPCOM 19-DEC-1994 08:56:39.27 %%%%%%%%%%%
(from node MYNODE at 19-DEC-1994 08:56:39.30)
Message from user SMITH on MYNODE
Rdb Database USER2:[SMITH.WORK.AIJ]MF_PERSONNEL.RDB;1 Event Notification
Process 2082005F:1 exceeded 5 second stall: waiting for record 51:60:2 (EX)
The system operator notification message contains four lines.
Line 1 contains the OPCOM broadcast header message. Line 2
identifies the process running the RMU Show Statistics command
that sent the message. Line 3 identifies the database being
monitored. Line 4 identifies the process that triggered the
alarm, including the alarm interval and the stall message.
To establish an alarm interval for the Stall Messages screen, use
the Alarm=Interval qualifier.
If you specify the Nointeractive qualifier, bell notification is
disabled, but the broadcast message remains enabled.