Message Flood Automation has the following limitations:

• It only counts the first (major) line of multi-line messages.
• It does not handle branch-entry messages until they are re-issued as normal messages. It cannot affect them while they are being queued for re-issue.
• It specifically ignores IEF196I and IEF170I messages.

  IEF170I

  A write-to-programmer message operation failed. The IEF170I message includes the reason for the failure and 53 characters of the failing message's text.

  IEF196I

  A message from a task started under the Master Subsystem (MSTR) is being written to the system log because it could not be written to the system message data set or joblog data set. The IEF196I message includes the message ID and text of the failing message.

• It does not receive control for WTOR messages.

If Message Flood Automation does not take action against a message, it is often because of these restrictions.