Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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
Workspace z/OS
Categories BCP_XCF/XES
Created by Guest
Created on Nov 9, 2015

Round robin scheduling of SRBs to CF list connectors

z/OS will always process the list notifications on a given system in the same order. It steps through the queue of structures that have active connectors on the system, one at a time, looking for structures that have list notification users; and then it steps through the queue of connectors to the structure who have actually received a pending list notification signal, one at a time, scheduling off an asynchronous SRB routine to that connector's address space to process the notification and drive the connector's list transition exit as it goes. Since the order of this queue of connectors to a structure on a given system is always a function of the order in which they connected, one of the connectors always gets looked at (and assuming both notifications have already arrived, gets his SRB routine scheduled to run) first. The second connector in this queue, other things being equal, is at a disadvantage.

Our application is pulling work from list structures and the work is not evenly distributed due to the scheduling of the SRBs to the connectors in the same order. Changing the scheduling to a round robin approach will allow the work to be more evenly distributed.

Idea priority High
  • Guest
    Reply
    |
    Nov 10, 2015

    Creating a new RFE based on Community RFE #79517 in product z/OS.