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 Open Access TM
Created by Guest
Created on Aug 19, 2015

Protocol message to inform Resume Tpipe client with /STO TMEM xxxx TPIPE yyyy is entered

We occasionally have to dequeue Tpipes, usually because a client process is not operational or running slowly. The deque process involves a /STO, /DEQ, /STA sequence of IMS commands. If the IMS Connect client is connected while this takes place, it doesn't know the Resume Tpipe in OTMA has been cancelled (due to the /STO TMEM xxxx TPIPE yyyy), and has to wait for its IRM_TIMER to expire (up to 10 minutes in our case). We have thousands of IMS Connect clients, and they're all automated for the most part, so restarting the process (with the cancel client ID bit on) isn't really an option. The client has to wait for the IRM_TIMER to expire before connecting again. This looks like an up to 10 minute "black hole" in processing for an otherwise busy process.

Idea priority Medium
  • Guest
    Reply
    |
    Jul 24, 2018

    Hi Derek Baessler,

    We've decided that this is a defect (as opposed a request for enhancement).
    We have gone ahead and created APAR PI97407.
    The current target date for this APAR is 9/16.
    You can track the APAR.
    And we'll go ahead and close this RFE.
    Email me directly if you have any questions.

    With warm regards,
    Deepak Kohli
    deepakk@us.ibm.com

  • Guest
    Reply
    |
    Dec 5, 2017

    Hi Derek Baessler,

    Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.

    When choosing new features to add from the list of requirements in our backlog, we assess which will bring the most value to as many clients as possible and prioritize those.

    After reviewing this request for enhancement and assessing its potential value, our decision is to add this item to our backlog. Items in our backlog are expected to be delivered within the next 18 months. We reserve the right to re-prioritize our backlog items as new requests come in. This helps ensure that we are constantly focused on providing the best value to all of our clients.


    Have a great day!
    Daphne Isom - dsteele4@us.ibm.com