Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Nov 8, 2022

Enable connection pooling for remote nodes when using CDPLEX

We use the PARSESS ADJACENT.NODE statement to limit parallel sessions from the local node to a remote node based on capacity as agreed with the partner node. When updating our environment to use CDPLEX with multiple server regions, this parameter is now independently managed by each local server. In order to maintain the same total parallel sessions to remote nodes when adding a second transfer region, we've had to reduce the PARSESS value by 50% to avoid potentially overwhelming a partner node. This works when both server regions are available, but when one region is down for reboot or any other reason, our capacity to remote hosts is reduced by half.

A better solution would be to have this value be shared amongst participating servers in an CD PLEX such that the PARSESS value is pooled and defines the sum total of sessions that can be running at any given time amongst all server tasks to a given SNODE.

What is your industry? Financial Markets
How will this idea be used?

Will be used to better use our available capacity during work windows where not all of our server tasks are up and processing workload

  • Guest
    Dec 16, 2022


    Are there any other ideas on the table to solve this problem? This is a real challenge for us in that we carefully negotiate parallel session values with our busiest partners such that we do not overwhelm one another during peak usage. Having to split that value by the number of servers we are running is much less than ideal. We are planning to expand the number of servers we are running and are now having to further subdivide or renegotiate this value. It would be much more preferable to handle this at the node/plex level and not at the individual server level.


  • Admin
    Chris Sanders
    Dec 16, 2022

    Thank you for opening this enhancement request with IBM. I have reviewed it thoroughly with my team. Unfortunately we won't be able to accept this request. This is due to the complexity of the request and potential to introduce complex defects that could impact our broader user base. With that said, we do expect that PLEX failover capabilities should really be able to rapidly recover if a node in the PLEX goes down. If you are not seeing this I would encourage you to open a case with our support team to seek guidance on configuration.


    Chris Sanders

    Connect:Direct Product Manager