Message flood automation processing is driven by the issuance of a message. As soon as that message is created, it obtains a timestamp, and this occurs before the message is seen by Message Flood Automation. If Message Flood Automation makes a decision based on that message, it interrupts the processing of that message until it has taken whatever action it needs to take. Once that has occurred, processing of the original message by the operating system is then allowed to resume.
In the following example, the second IOS100I message caused Message Flood Automation to exceed the REGULAR message threshold. Further processing of the second IOS100I message was then suspended while:
11:14:58.79 ... 00000010 IOS100I DEVICE 891B BOXED, LAST PATH 75 LOST
11:14:58.91 ... 00000010 CNZZ002E MESSAGE THRESHOLD REACHED FOR JOB NONAME
11:14:58.79 ... 00080A09 IOS100I DEVICE 891C BOXED, LAST PATH 75 LOST