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
Created by Guest
Created on Oct 26, 2023

TCPIP Sysplex Ditributor SERVERWLM low weights management

We have a large database ( 6 DB2 members, more than 10000 DB2 transactions per second) where DDF TCP traffic is balanced with VIPA SERVERWLM algorithm.

In normal condition WLM weights are high enough to spread new sockets in a balanced way. When there is lack of resources it is possible that WLM returns weight 1 for one member and 0 for the others.

From a capacity point of view all members have a similar ( very low ) capacity to process workload. In this scenario Sysplex Distributor routes ALL new incoming sockets to only one member until the weights are refreshed.

If this happens in peak of connections, this is dangerous for service stability.

From a service point of view all systems should be managed as "equal" (like all in 0 weight), routing the workload in round robin.

We opened case TS014380133 to WLM, the response was that this low weights scenario needs to be managed by the exploiter (TCPIP).

Our idea is to implement a new parameter MINIMUM_WEIGHT ( default 0 ), where customer can force Sysplex Distributor a weight as 0.

For example MINIMUM_WEIGHT=2, a 6 member routing weight list of 0 / 0 / 1 / 2 / 0 / 0 will be managed as 0 / 0 / 0 / 0 / 0 / 0.

Thanks

Idea priority High