Suppress alarms and events on flushed or aborted commands

Note: For information on overriding default configuration settings, refer to Modify configuration settings.

Follow this procedure to prevent the generation of alarms and the logging of events when the system flushes or aborts certain commands.

Some flushed or aborted commands, such as the offscan command, do not require any Controller interaction and require suppression because they would be considered nuisance alarms and events. However, other flushed or aborted commands, such as an analog setpoint command, do require alarms and events.

The reasons for flushing or aborting queued or in-progress commands include the following:

• A connection or remote is taken offscan

• RealTime service failover

• Change in DistribuSys ownership

To suppress alarms and events on flushed or aborted commands

1. In the %DNADataRoot%\RealTime\config\Settings directory, either create or open the RealTime_SuppressAbortedCommandAlarm.json file.

2. For the value, enter the command request type for which you want to suppress alarms and events should the system flush or abort the commands.

   Separate each command request type with a comma. For example:

   "RealTime" > "SUPPRESS_ALARM_FOR_ABORTED_COMMANDS": "SCH_OFFSCAN,SCH_INTEGRITY"

3. Save the file.

4. Restart the RealTime service.

   Note: If the RealTime_SuppressAbortedCommandAlarm.json file doesn't exist on the system, offscan alarms are suppressed by default.