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
Workspace z/OS Connect
Created by Guest
Created on Jan 7, 2021

Enhance MQ Service Provider for z/OS Connect to set message priority

Please enhance the MQ Service Provider for z/OS Connect and the z/OS Connect API Toolket to set the message priority for MQ Services.

Idea priority High
  • Guest
    Reply
    |
    Jun 30, 2021

    Thank you for this RFE.

    On the 20th April we added a comment describing how this use case could be satisfied using technology that exists in the product today. We ask if this approach meets your needs and have not received any further comments detailing what would be needed above and beyond the solution we described. Correspondingly this requirement is being declined at this time. You have an opportunity to resubmit in twelve months time if you wish it to be considered then.

  • Guest
    Reply
    |
    Apr 20, 2021

    Thank you for the reply.

    It would be useful to know how many distinct priorities you would expect to be used from a single z/OS Connect EE server?

    If the number is relatively low (eg <10), then one approach to solving this problem with the config described would be to define an MQ connection for each distinct priority (eg MQConnHigh, MQConnMed, MQConnLow) and then use a policy to select which connectionRef to use for any given request based on the value of header on the request. This would also allow you to set a default connectionRef (and therefor priority) for each service in the case that the header is not provided.

    More information about z/OS Connect EE policies can be found here:
    https://www.ibm.com/docs/en/zosconnect/3.0?topic=apis-administering-zos-connect-ee-policies

    Please let us know if this approach meets your needs.

  • Guest
    Reply
    |
    Apr 5, 2021

    Okay, it seems that I have overlooked this attribute, because I expected such a property in the MQ service definition. To me it doesn't appear like an ideal solution. The same queue may be used for a lot of different messages with different priorities. Our customers have lots of such queues - for instance queues used to trigger transactions in IMS, where the messages for the more important transactions are getting a higher priority, or queues used to send requests to long running batch applications, where heartbeat check / monitoring / config change messages have a very high priority and real business request messages have a priority depending on their importance respectively depending on the maximum allowable response time. That means if we need to use this attribute, we would need to have multiple definitions for the same queue with different priorities in the server.xml. It would be much better, if this could be defined with the MQ service. Ideally it could be also overwritten using the policy support. With that the same queue definition and the same service definition could be used even if there is a need to prioritize some service requests higher than usual.

  • Guest
    Reply
    |
    Mar 30, 2021

    Thank you for this RFE.

    It is possible to set MQ message priority in z/OS Connect EE APIs today using the "priority" attribute of the properties.wmqJms sub-element within the jmsQueue element in server.xml:
    https://www.ibm.com/support/knowledgecenter/SS7K4U_liberty/com.ibm.websphere.liberty.autogen.zos.doc/ae/rwlp_config_jmsQueue.html#properties.wmqJms



    See the "properties.wmqJms" section.

    Using this functionality you can set the priority of messages from z/OS Connect EE.

    If this functionality does not satisfy the use case described in this RFE, it would be useful to understand what capability is required in addition to the functionality available in the product today.