Message Flood Automation and EMCS consoles

Message Flood Automation processing occurs before a message is queued to Extended MCS (EMCS) consoles. Because EMCS console interfaces can be used by automation products such as NetView®, there are special considerations:

• If a message flood occurs, and Message Flood Automation has been requested to suppress the message from display, the message is not queued to any EMCS console unless automation of the message has been requested (typically by specifying AUTO on the message's MPFLSTxx entry).
• If a message flood occurs, and Message Flood Automation has been requested to suppress the message from display and NOT automate it, the message is not queued to any EMCS console.

Note that the decisions to log, display or automate a message are independent decisions. It is possible (and might be desirable) to obtain messages at EMCS consoles for automation purposes without logging or displaying them.

If the NetView MSGIFAC parameter is set to SYSTEM, NetView obtains all messages for automation processing from the EMCS console interfaces. (If the MSGIFAC parameter is set to SSIEXT, NetView only obtains command response messages from the EMCS console interfaces; unsolicited messages are obtained from the SSI). The messages that NetView "sees" at the EMCS console interface have already been processed by both Message Flood Automation and z/OS® deletion, logging and console queuing processing.