Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Jul 25, 2019

Improve persistent thread concurrency

With the implementation of transactions with persistent threads (like pseudo wait-for-input on IMS) we have been facing some concurrency issues in our site, specially with HPU and batch programs that perform lock escalation. This happens because the persistent thread claims an intent lock on the table/partition and, since our plans have the parameter RELEASE set to DEALLOCATE, never releases it. Programs that try to claim non-intent locks on the table/partition used by persistent threads get a timeout.

Previously the concurrency issues were worse because no utility could run against tables that were acessed by persistent threads, but the problem was solved with the introduction of the PKGREL_COMMIT parameter on v11.

To solve the concurrency issues, we propose a similar behavior as introduced by the PKGREL_COMMIT parameter: dynamically changing the RELEASE parameter (from DEALLOCATE to COMMIT) when a process claims a non-intent lock on the table/partition used by the persistent thread.

 

Itau-Unibanco S.A.

  • Admin
    Janet Figone
    Dec 10, 2020

    Thank you for submitting this Db2 for z/OS enhancement request.

    After giving the request a comprehensive review, we have determined that we cannot include it as a candidate in an upcoming product deliverable because the request has a high implementation cost with a low relative value. As a consequence we will not be implementing this request.

    We appreciate your input to the Db2 for z/OS development team. We also hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of Db2 for z/OS.

    Sincerely,

    Db2 for z/OS Team

  • Admin
    Janet Figone
    Oct 16, 2020

    Hello, Yes. The additional input you provided has been shared with the Db2 for z/OS developer reviewing this idea. We will let you know if any additional information is needed. Thank you.

  • Guest
    Aug 14, 2020

    Hello, Janet.

    Did you see our last update on November 21, 2019 ?

    Is it enough to allow analysis proceed or do you need/want more information ?

    IDEA is NEED MORE INFORMATION.

    Could you let us know, please ?

  • Guest
    Nov 21, 2019

    Hello, Janet.

    Here is a scenario:
    Transaction 1 updates records in the table A. Since transaction 1 is in a PWFI (pseudo wait-for-input) IMS region (the program will never be deallocated) and its plan is bound with the release parameter set to "deallocate", an IX (intent exclusive) lock will be constantly held on the table A. Then, the batch program 2 tries to scan table A with read stability, but since it claims many READ row locks it will try to escalate its locks to a table shared lock. This will cause program 2 to receive a timeout or deadlock message, since the shared lock will never be obtained on table A because of the release parameter on the transaction 1. The same would happen when running a HPU with LOCK YES on table A.

    We would like to know if it is possible to change the behaviour of the release parameter to dynamically change to "COMMIT" on a plan whenever a non-intent lock is requested on an object that has locks held by it. That way, program 2 would claim a shared lock on table A and the release parameter on transaction 1 would dynamically change to "COMMIT", allowing it to release the locks held on table A on the next commit.

  • Admin
    Janet Figone
    Nov 21, 2019

    Thank you for submitting this Idea. We have reviewed it and would like to ask if you can please send in a detailed scenario, perhaps with messages, or anything providing more details. Thank you.