Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
Created by Guest
Created on Aug 13, 2024

Cluster Monitoring Program AMQSCLM to support CLUSNL as well

Cluster Monitoring currently works only if a cluster queue belong to only one cluster.


Working Scenario: Cluster queue defined using CLUSTER Param


When we use amqsclm, the cluster monitor on a cluster queue which is a part of only one cluster it works well i.e. when we define a queue with param CLUSTER.


CLWLPRTY is set to 1 when there is a reader on a queue instance.


Not Working Scenario: Cluster queue defined using CLUSNL Param


Amqsclm is not working on a queue with is a part of multiple clusters. The cluster queue is defined with the param CLUSNL. There is no option to use amqsclm to use CLUSNL, so using only one of the cluster the queue belongs to.


CLWLPRTY is not changing when there is a read on a queue instance.


Error from the amqsclm logs

CLM0051E No queues found of name '<Queue_Name>' in cluster '<Cluster_Name> '08/12/20 The above is error from the Cluster Monitoring logs


In this case I am using the cluster monitor to monitor the queue using one of the clusters which it belongs.

Idea priority High
  • Admin
    Mark Taylor
    Reply
    |
    Aug 20, 2024

    This is not something that we would expect to include in the product. However, the source code for amqsclm is shipped with MQ so it is possible for you to modify the sample program to match your specific requirements.