Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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
Categories Other
Created by Guest
Created on Jan 20, 2016

Need MQ shared message consumption to be responsive to CICSplex workload balancing signals

We have two MQ application patterns which are unresponsive to workload balancing.

Pattern 1
An application 1) reads a message from a shared MQ queue, 2) starts a new CICS transaction to process the message, and 3) return to step 1. The application is hosted in multiple CICS regions across the CICSplex.

Pattern 2
An application starts multiple CICS transactions, each reading from a single shared MQ queue. This application is hosted in multiple CICS regions across the CICSplex. The transaction waits for and reads one MQ message, completely processes that message, and then starts a new copy of the transaction.

Both of these patterns exhibit the same characteristic, that an MQ GET against a shared queue is a simple first-in first-out algorithm, and is NOT responsive to either CPSM or WLM workload balancing signals. There are no tuning capabilities to influence how MQ GET selection can be distributed amongst active “GETters”.

We want the “system” to take action automatically to avoid problems with importance 1 work in a sysplex, rather than require customers to take manual intervention to address this.

Idea priority High
  • Guest
    Reply
    |
    Apr 26, 2016

    This requirement has been evaluated. Looking at current plans, it is not likely that this would be implemented in the next two CICS TS releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in twelve months time if you wish it to be considered then.

  • Guest
    Reply
    |
    Feb 24, 2016

    MQ does not do workload distribution and it is difficult to see how it could be made to.

    Instead, in the scenarios described in the RFE, we recommend you use CPSM to distribute work across the available CICS regions by routing each START request to the most appropriate region (AOR). Alternatively you can code a CICS dynamic routing exit that incorporates whatever load distribution criteria you need.

    Having the workload distribution in CICS is simple and effective. It is unlikely that any solution based on MQ doing workload distribution would be as good, even if it could be made available in a reasonable time-frame.

  • Guest
    Reply
    |
    Feb 5, 2016

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server
    Component - Other
    Operating system - IBM z/OS
    Source - zBLC

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - zBLC family
    Product - zBLC
    Component - zBLC Requirements
    Operating system - IBM z/OS
    Source - zBLC