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
Categories z/TPF
Created by Guest
Created on Apr 17, 2014

Enhance ENQC support and provide greater visibility/alerting into the number of ECBs waiting on events

1) There is no means currently for an application to know how many ECBs are waiting on a resource. This means that applications have only two processing options for ENQC 1) if they get the resource
or 2) if they don't get the resource.

Additional processing options are needed that allow an application to take an alternative processing path if the resource is currently held and the number of ECBs waiting on the resource exceeds an acceptable value. This would allow an application to avoid significant backlogs if an alternative processing path were available to it. It would be up to the application to determine what the “acceptable” number of waiters was, but enhancements to the ENQC API are needed such that it :
a) can optionally return the number of waiters if a resource is currently held
b) accepts a MAXWAITER and MAXWAITERERR parameter so that the ECB is queued on a held resource only if the number of waiting ECBs is less than the specified MAXWAITER value. The MAXWAITERERR parm would provide a branch location to indicate that the resource was held because it was already held and the number of waiting ECBs was greater than the MAXWAITER value specified.

2) The count of waiting ECBs for any given type of event in the event table has to be determined by counting the number of chained SWBs. A count of waiting ECBs should be added to the event table item. This would allow
a) fast support for the ENQC enhancement in item 1 above
b) allow ZDEVN to immediately access the waiter count without chasing SWB chains
c) provide the infrastructure for alerting based on number of waiters (see point 3 below).

3) We need to be able to alert on event table waiters exceeding a user defined value, much like we can currently alert on RHT waiters. The alert would not take any action, it would be a warning mechanism of contention build up. User exits in the support might be useful, but the default action for events that had long queues of waiters should be only to report.

Idea priority High
  • Guest
    Reply
    |
    Mar 15, 2023
    Based on priorities and resources, IBM does not intend to implement this in the foreseeable future.
  • Guest
    Reply
    |
    Oct 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/TPF

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - z/TPF

  • Guest
    Reply
    |
    Jun 11, 2014

    RFEs 54711 and 54709 created to document items 2 and 3 separately as requested.

  • Guest
    Reply
    |
    Jun 10, 2014

    Please open 2 additional RFEs for items #2 and #3. This will be implemented in stages.