If the Message Flood Automation policy for the message is NOLOG, NOAUTO and NODISPLAY, the message will cease to exist after it returns from the SSI. The combination of these three is functionally equivalent to setting the CTXTRDTM bit in an MPF exit. The point is that the message does not cease to exist until it gets back from the SSI; it is up to every subsystem that looks at WTOs (WQEs) on the SSI to determine that a message has been marked for deletion and ignore the message if it so chooses.
Not all products receive their messages through the SSI. Some front-end the WTO SVC which occurs before Message Flood Automation has seen the message. Such products will be oblivious to any changes made to the message by Message Flood Automation. Some products receive their messages through the EMCS interfaces. These products will not see any messages that are deleted (NOLOG, NOAUTO, NODISPLAY) by Message Flood Automation; they will see any messages for which the Message Flood Automation policy specifies AUTO (even if the message is not to be logged and is not to be displayed on an operator console). W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
