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 Runtime
Created by Guest
Created on Nov 20, 2020

Update TSQ API to allow a distinction between TS MAIN vs. pooled queues

We ran into an issue with CICS regions having TSQ's with the same name in both TS MAIN and in the TSQ shared pools.

This introduced all kinds of challenges where for example we look at the last used interval on the pooled queue, and then want to issue a TSQ DELETE on this pooled queue if it is over a certain age. When we issue the TSQ DELETE it deletes the TS MAIN queue and not the pooled queues.

The same issues will exist for READ and WRITE to TSQs.

Can the TSQ API be improved by adding an additional option to identify if the specific TSQ request should be MAIN/AUX/POOL. This will assist in overcoming this default behavior and prevent us from deleting the incorrect queue.

Idea priority Medium
  • Guest
    Reply
    |
    Jan 29, 2021

    We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.