Use this section to specify the DECnet phase V event log that the Mail Monitor will scan. You need to make a separate entry for each named event. In other words, the configuration file should have a separate EventLog section for each Event=event-text that you need to monitor.
The scanning module for any entity that is controlled by means of the Network Command Language (NCL) parses the DECnet event file. and produces the following records:
which is the command to use that determines the filename of the event log.
which defines which event name in the event log will trigger a monitor record, regardless of the setting of Full_Log.
which overrides the command specified above, using a specific filename for the event log.
which is a descriptive name of events being reported in the event log.
which determines whether to report all events concerning the entity entity-name, without regard to the event being monitored (specified by Event=event-text).
which determines which fields from the event record will be reported in the Status field of the monitor record. Any fields of the event record containing this text will be added to the Status field.
which determines which fields from the event record will be reported in the Status field of the monitor record. Any fields of the event record containing this text will be added to the Status field.
For example:
[EventLog XMR1] Entity_Name=XMR Command=mc ncl show event dispatcher sink local_sink file name Full_Name=MAILbus 400 Message Router Gateway Full_Log=on Severity=4 Event=MTA Access Error Identifier=Operation Status=Problem