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 (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
Created by Guest
Created on Jun 30, 2022

Address $$UPDATE Deficiencies

We experienced an issue with C:D 6.1 on z/OS where we performed a $$UPDATE function on a netmap entry and the node became unable to accept inbound connections. We were advised by CD support that there is an obscure recommendation in the documentation to not perform UPDATE on netmap entries with LDNS coded, but instead do $$REPLACE or $$DELETE/$$INSERT.


If IBM will not fix the underlying issue, we would like a check to be perfomed when doing an UPDATE to reject the operation if destination on the netmap entry is defined by LDNS. This will prevent future issues for other customers unaware of this behavior.

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

Will prevent outages caused by administrators unaware of this obscure recommendation.