This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
All GA versions
How do you control the MainView AutoOperator rules processor to handle the suppressed messages specified in the MPFLSTxx system member.
The parameter HONORMPF in the member AAOPRMxx of the BBIPARM library, is used to control how the MPFLSTxx system member is handeled by the AO rules processor.
HONORMPF=(Y,N) the default is N Determines whether messages will be handled by the AO rules processor or not when the MPF suppression flag is set.
Honor MPF Suppression - YES Any message suppressed by MPF will not be presented to the AO Rule Processor. The message will not appear in the AO Event Activity Statistics.
- NO All messages will be presented to the AO Rule Processor regardless of any action MPF may have taken with the message.
There is an additional parameter MPFFILTR also in the AAOPRMxx member to handle the MPF definition.
Note : If HONORMPF=YES is set, MainView AutoOPERATOR ignores any settings on the MPFFILTR parameter.
If MPFFILTR is not specified, all messages will be input to rules.
MPFFILTR=((SUP=YES|NO|*,AUTO=YES|NO|TOKEN|*)) - Specifies the MPF SUP and AUTO values to use when determining which MVS messages are eligible for automation.
- Only the messages with SUPand AUTO values matching one of the pairs specified will be input to rules.
- A maximum of four pairs can be specified.
- Each pair must be enclosed in parenthesis.
If the MPFFILTR parameter is set
only WTOs that have both AUTO and SUP set to NO are eligible for MainView AutoOPERATOR automation. MainView AutoOPERATOR ignores all other messages that have different AUTO and SUP settings; they are not eligible for MainView AutoOPERATOR automation.