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
Created by Guest
Created on Aug 16, 2018

IMS Sysprog

IRLM deadlock report does not include a Unit of work (UOW)or Unit of recovery (UOR) token for the transactions involved in the deadlock.
Application programmers often request for input messages of the transaction when investigating the deadlocks. Because the record on the database for the lock concerned does not necessarily include information that can be tied up to the input message, locating the x'01' record becomes difficult.
Also the pseudo IMS abend further complicates the issue as IMS dynamically reschedules the transaction that was terminated to resolve the deadlock. There is no indicator on the input records (x'01') to say a transaction is one that was rescheduled from a previous deadlock.
Current process to track the originating message includes running reports for transactions with higher than normal elapsed time, filtering them and then evaluating the databases they update and attempt to tie up the deadlock to the input message. This is very time consuming.

Idea priority Medium
  • Guest
    Reply
    |
    May 9, 2020

    Hi,
    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.

    At this time, after re-reviewing this request for enhancement and assessing its potential value, we have decided to reject it. We think it’s a great idea but we are rejecting RFE 123679 because we don’t feel we can deliver it within the next 18-24 months which is the goal we have set for RFE deliverables as part of our IMS Gold program. You are welcome to resubmit this RFE at a later date and we will reconsider.

    We appreciate your input to IMS, and we hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of IMS.
    Thank you.
    Sincerely,
    Deepak Kohli - deepakk@us.ibm.com

  • Guest
    Reply
    |
    Mar 13, 2019

    Hi ,

    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!
    Deepak Kohli – deepakk@us.ibm.com