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 Future consideration
Categories z/TPF
Created by Guest
Created on Apr 1, 2021

TPFUG: Provide z/TPF zMQ API that returns the associated Remote or Local zMQ Name(s) for a specified zMQ Dynamic Queue Name

1. It is necessary to be able to enquire on the z/TPF Resources used by zMQQs associated with z/TPF zEVent processing, particularly z/TPF System Work Blocks (zSWB) usage and zMQDepth.
2. For this to be done all local, remote, aliased, dynamic zMQQs as well as those in the z/TPF MQ Dynamic Routing Table (zMQDRT) must be queried.
3. In some cases, the provided queue name is a Dynamic Name that must be converted to its associated local or transmit zMQQ Name.
4. A z/TPF zMQ API is needed to return local or transmit zMQQ Names for a Dynamic zMQQ Name or those on the z/TPF MQ Dynamic Routing Table (zMQDRT). The following are needed based upon the zMQDRT's Queue Types:
a. If zMQDRT's zMQQ Type = "Alias: then the Target zMQQ Name must be returned.
b. If zMQDRT's zMQQ Type = "Remote" then the Remote Queue Manager's Name, Remote Queue's Name, and the local Transmit Queue Name needs to be returned.

Idea priority High