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
Created by Guest
Created on Mar 3, 2022

Enhance Capability of DFSNDMX0 Exit

1) Pass information to exit to indicate if a deadlock abend was due to an ESS deadlock.

Business value: DB2 handles lock timeouts on object locks, such as tablespace locks, as deadlocks
These are persistent conditions, a retry of the transaction is not likely to be successful.
Retrying creates a very long response time for the message involved and also ties up
dependent region for prolonged periods, impacting other work.
DFSNDXM0 can be used to discard such messages rather than retrying them

2) Pass information to the exit to indicate if the message involved is a retry.

Business value: To discriminate between deadlock conditions likely to be resolved on
retry and those likely to fail again, it is useful to know if the failing message has already been retried

3) Provide capability to discard an IFP message
Business value - for the reasons described above, it may be desirably to prevent repeated retries
of transaction messages. Current implementation does not allow this for IFP messages


4) Invoke the exit when there is a no message condition. An example a /STO REG ABDUMP command
targeting a PWFI MPP. The transaction instance waiting on GU abends U0474, and DFSNDMX0 cannot
be used to restart it. This complicates customer automation.

Idea priority High
  • Guest
    Reply
    |
    May 31, 2023
    Thank you for your interest in keeping IMS a vital and successful product. 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.

    Upon further review this request for enhancement, we have decided to reject item #3 (Provide capability to discard an IFP message) because of technical feasibility on how IFP message queue is managing the retry process. The requested change may incur additional overhead for processing.

    For item #1, 2 and 4, we would add them to the backlog for future review and considerations.

    Thank you for your continued support with IMS. If you have any further question, please contact us.