Current Queue Manager Status performance considerations

Version 7.1 introduced some new attributes for the real-time queue and channel performance metrics to the Current Queue Manager Status (QMCURSTAT) attribute group. With the new functionality, the Current Queue Manager Status attributes can be used to determine and provide the overall overview of the health of your queue manager including the health of its queues and channels. Data collection of these attributes needs to inquire the attributes of every queue or channel. This data collection might cause high CPU usage when the monitored queue manager has many queues or channels.

When the following symptoms appear in your environment, consider checking the use of these Current® Queue Manager Status attributes and disabling the unnecessary data collection:

  • Considerable increase on CPU resource assumption in comparison to prior releases
  • Slow response for the Current Queue Manager Status workspace

The use of the Current Queue Manager Status attributes can impact the performance from the following queries:

For detailed information about the CHLTHRESH and QTHRESH specifications and about the health overview attributes, see Current Queue Manager Status attributes.

Situations

If you have customized situations on the Current Queue Manager Status attribute group, review the situation definitions. Try to minimize the number of the situations that might cause the real-time queue or channel metrics to be collected. Combine such situations if possible.

To understand the impact of Current Queue Manager Status attributes on situation filters, see Current Queue Manager Status attribute considerations.

Workspaces on Tivoli Enterprise Portal

On Tivoli Enterprise Portal, each time when the Current Queue Manager Status workspace is displayed or refreshed, real-time queue and channel metrics are collected.

You might have your own customized workspace that issues a query to the Current Queue Manager Status attribute group. If these workspaces are frequently used, update the associated query to use the filters of CHLTHRESH='NONE' and QTHRESH='NONE' to disable the data collection of real-time queue and channel metrics if possible. Note without such a change, your customized workspaces in the releases earlier than version 7.1 can cause the real-time queue and channel data to be collected even if they are not useful.

Historical data collection

History data collection on the Current Queue Manager Status attribute group usually does not cause performance issues because the collection interval is much longer in comparison to situations. However, if you are not interested in the new attributes that are introduced in the version 7.1 in the history data collection and want to improve the performance, you can disable the real-time queue and channel metrics data collection when you configure historical data collection.

To do this, specify the CHLTHRESH='NONE' and QTHRESH='NONE' formulas in the Filter tab of the History Collection Configuration window.

Likewise, you can use the same way to set thresholds for the QTHRESH and CHLTHRESH attributes to override the default for the determination of health-related metrics according to your site's requirements.

Remember: Do not use the QTHRESH or CHLTHRESH attributes in the filter in a query to retrieve historical data either in short-term files (PDS on z/OS® systems) or in the warehouse. Otherwise, the likelihood of no rows being returned matching the query is high. If the QTHRESH or CHLTHRESH attribute is specified, their values in historical data rows must match whatever is specified in the historical collection query filter so that data can be returned. Therefore, it is better not to specify those filters on any query to retrieve the data for viewing.

Enhanced 3270 user interface (z/OS systems only)

For the Enhanced 3270 user interface, the product provided workspaces collect real-time queue and channel metrics only when required. You might have your own created workspaces that issue a query to the Current Queue Manager Status attribute group. For such workspaces, review the selected attributes in the SQL query and add the filter of CHLTHRESH='NONE', QTHRESH='NONE', or both to improve the performance.

Furthermore, a single set of the threshold values is used throughout all the product provided workspaces that issue queries to the Current Queue Manager Status attribute group. You can even set your own threshold values by using the interface profile. If required, you can create your own workspace that takes the same set of threshold values. Refer to TKANWENU(KMQQMSTS) and TKANEXEC(KMQTHRDI) as the example.

For information about how to customize the Enhanced 3270 user interface, see Customizing the Enhanced 3270 user interface.