What are the considerations/recommendations for defining alarms with MainView for Websphere MQ?

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    MainView for MQ


    MainView for WebSphere MQ


    What are the considerations/recommendations for defining alarms with MainView for Websphere MQ?

    We have seen some issues at customer sites where incorrectly coded alarms have caused unnecessary cpu overhead in the MainView for Websphere MQ Product Address Space.

    LP: MainView for WebSphere MQ




    Legacy ID:KA403839


    Defining alarms with MainView for WebSphere MQ


    When you define an alarm, the following variables can affect how efficiently data is gathered for evaluation by the alarm:

    • Total number of objects
    • Number of objects you are monitoring
    • Number of concurrent requests to a Queue Manager
    • Context specified in the alarm

    Carefully considering these variables can help you define alarms that use the least CPU time, and create alarm requests that do not time out before data is returned to the alarm.


    For example, on most views, an object name is passed as a parameter to MainView for Websphere MQ and to the Queue Manager (when the request is made).


    Issuing the command LQ ABC* uses the equivalent programmable command format (PCF) as issuing DIS QLOCAL(ABC*). However, LQ ABC* allows you to limit the volume of messages written to the queue: MQSeries returns only queue names that begin with ABC. This filtering reduces the number of messages read by MainView for Websphere MQ and requires less parsing.


    Therefore, depending on how many objects fit the rule you are applying, you might want to use a filter parameter instead of a where clause. Typically, using a where clause is preferable if the alarm that you are defining will apply to a majority of object types.


    Chapter 4 of the MainView for Websphere MQ User Guide (Usage Scenarios), provides a number of examples on how to correctly code alarms:

    • Correctly using the where clause to create an alarm
    • Incorrectly using a where clause that wastes system resources
    • Correctly using the parameter field (instead of using the where clause)

    If you are in doubt or require further assistance, please raise an issue with BMC Customer Support.

    Related Products:  
    1. MainView Infrastructure


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles