Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Implementing support for MPF

This topic describes how 

BMC AMI Ops Automation

 can coexist with the MVS Message Processing Facility (MPF). 

The MVS Message Processing Facility (MPF) allows you to modify the attributes of write-to-operator messages (WTOs). For example, with MPF you can modify the appearance of a WTO (such as its color and highlighting) and suppress messages from consoles.
 

Previous releases of BMC AMI OpsA provided the HONORMPF=(YES | NO) parameter, which determined how the product automated WTOs with the MPF SUP keyword setting.

  • If HONORMPF is set to the default value of NO, all WTOs are eligible for BMC AMI OpsA automation (regardless of how the SUP keyword is set on the WTO):

    HONORMPF=NO


  • If HONORMPF is set to YES, only WTOs with the SUP keyword set to NO are eligible for BMC AMI OpsA automatiion:

    HONORMPF=YES 

You can specify that BMC AMI OpsA will determine which WTOs are eligible for automation by checking the WTO for both the SUP and the AUTO keyword setting. The possible values of the MPF AUTO keyword are:

AUTO=(YES|NO|token)

where token is an up to 8-character user-specified token name. The token name can contain wildcards and blanks.

The possible values of the MPF SUP keyword are

SUP=(YES| NO)

Note

For more information about MPF, see the IBM publication MVS Initialization and Tuning Reference.

To check a WTO for its AUTO and SUP settings, use the MPFFILTR= parameter in BBPARM member AAOPRM00. For more information, see Implementation-considerations-for-MPF.

This section contains the following topics:


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*