Description:
OPSMVS will not be affected since we do not pay attention to the automation processing bit they would be setting.
Solution:
Message Flood Automation is implemented as a Message Processing Facility (MPF) IEAVMXIT routine that is called as a part of z/OS WTO processing. The exit examines each message in the z/OS system, and attempts to identify when too many WTOs are being issued and by whom. It then takes appropriate action - usually to suppress the message from display at a z/OS console, and to indicate that automation processing is not required. It can also issue commands e.g. to cancel the user or process.
OPSMVS will not be affected since we do not pay attention to the automation processing bit they would be setting.
Message Flood Automation suppresses message from the consoles not the SSI. If you need to send messages to consoles you can add up to 30 messages (no wildcards) to ignore for MFA.
Example:
/*-------------------------------------------------------------------*/ /* SPECIFIC message specifications. */ /* You can have up to 30 MSG entries. */ /*-------------------------------------------------------------------*/ SPECIFIC MSGTHRESH=50,MSGLIMIT=20,INTVLTIME=1 SPECIFIC SYSIMTIME=0.25 SPECIFIC MSGIMTIME=0.25 DEFAULT LOG,NOAUTO,NODISPLAY,NORETAIN MSG IOS001E MSG IOS003A MSG IOS050I MSG IOS051I MSG IOS071I MSG IOS251I MSG IOS444I MSG IOS450E MSG MOSXRC IGNORE MSG MOSMVS IGNORE MSG MOSONL IGNORE MSG MOSOPS IGNORE