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 Delivered
Categories Other
Created by Guest
Created on Apr 24, 2017

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
    |
    Dec 14, 2018

    This RFE is satisfied by CICS Transaction Server for z/OS V5.5 which is GA today 14th December 2018.

  • Guest
    Reply
    |
    Oct 2, 2018

    This RFE is satisfied by CICS Transaction Server for z/OS V5.5 which is announced today 2nd October 2018 and which has a planned availability date of 14th December 2018.
    For more information see the CICS TS V5.5 announcement letter https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS218-352/index.html&request_locale=en

  • Guest
    Reply
    |
    May 18, 2018

    Not the ability to deal with uneven LPAR capacity, but the ability to throttle back MQGETTERs when at maxtask is something we would like to address. The RFE is being moved into 'Planned for Future release' status. Please note:
    IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.