Considerations for message-flooding prevention

The following information shows the rules for suppressing messages through the message-flooding prevention table:

• The message is recorded in the VTAM® internal-trace table.
• The message is constructed, but is not transmitted to the operator. The message might be routed to other areas. For example, if you coded PPOLOG=YES in your start options, the message will be routed to the PPO (primary program operator) log.
• If the first line of a message group is suppressed, all messages in the group are also suppressed.
• A message within a message group cannot be suppressed by specifying that message on the FLDENT macroinstruction.
• USSMSG00 – USSMSG14 are not suppressed.

The message-flooding prevention process can cause some undesirable circumstances to occur. For example:

1. A command might be entered and result in a message to the operator. If the message is a member of the flooding-prevention table and the command is reentered within the designated time-span, the message might not appear the second time as expected.
2. If the header of a message group is suppressed, all messages in the group are also suppressed. The information in these messages might differ from the last issuance, but they are not reissued.