Suppress ACTION message when processing certain DEFACTNs

The Operations Manager DEFACTN defines an action to be taken when a rule (defined by DEFRULE) is triggered.  For actions triggered by a virtual machine console message, Operations Manager inserts a mandatory message into the virtual machine's console as well as in the Operations Manager log.

To improve visibility of virtual machine console messages, exposing them to other systems such as UNIX Syslog, Grafana Loki, or Splunk (or others), sending the console messages to some external system is desirable.  This can be done using a DEFRULE that selects all messages that appear on the console and then defining the action for that rule to be a REXX script or other transport that sends the message to the external system.  However, the use of DEFRULE/DEFACTN results in the mandatory ACTION message appearing in the virtual machine console for every line of console output.  The ACTION message makes the Operations Manager console for the virtual machine cluttered and hard to read.

Sending console output using DEFRULE/DEFACTN achieves the desired result, and the console messages arrive at the target external system as intended.  However because the Operations Manager console for the virtual machine is cluttered with ACTION messages, interacting with the virtual machine -- out of scope for the external system, which is intended to be a read-only view for messages and not interactive -- is severely compromised to the point of being almost unusable.

Alternatives to DEFRULE/DEFACTN, such as offline or batch processing of console messages via the Operations Manager log, reduce the effectiveness of the function due to the interval or batch delay -- sending console messages in a batch even as often as in one minute intervals would impact the effectiveness of the external sending.  For example, if the console message sending was intended to be used for security purposes (i.e. sending to SIEM for intrusion detection) the batch delay may be a security exposure. 

Removing the ACTION message for such processing is the idea.  Either of the following options is desirable:

• that the DEFACTN command be updated to allow optional suppression of the ACTION message, OR
• that a different method of defining an action to be performed for every line of virtual machine console output be created, such that the ACTION message generated by the trigger of a DEFACTN does not occur.