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


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

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


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Apr 1, 2021

Improving latch contention in Db2 z/OS

DB2 workloads run at a priority that is related to their origin (may it be batch, IMS, DDF, …) and according to WLM service class definitions.

In high system utilization scenarios, or due to workloads running in a WLM service class with a resource group maximum, it may well happen for a service class to be assigned to a very low priority, or even tasks may be marked non dispatchable in order to keep service class’ CPU utilization below the maximum defined to their resource group.

If a task can't have access to the CPU due to its low priority and it's holding a latch, even for a few seconds (2-5), contention may happen and undesired side effects could arise, as we’ve often observed in our OLTP.

Current contention notification seems too “slow” in trying to solve such situations, and there’s a noticeable negative impact to our highly response time sensitive online workload.

Blocked workload support has solved the problem to some extent, as we’re still facing latch contention episodes (even though we’ve set the BLWLINTHD to its minimum allowed value of 1) and this solution seems inelegant to us (we’re promoting all CPU blocked tasks, may they be holding latches or not, may they be high or low priority workloads…)

Needed by Date Dec 31, 2021
  • Admin
    Janet Figone
    Reply
    |
    Aug 24, 2021

    Dear Carlos, My sincerest apologies but the enhancement development is planning to implement is not going to solve the problem of 2-5 second latch waits. You will need to rely upon the system to ensure each task gets its fair share of CPU, but ultimately if the system remains severely constrained in terms of CPU then latch waits are an inevitable consequence. Therefore, unfortunately, we will be closing this idea as Not under consideration.

    Sincerely,

    The Db2 for z/OS Development team