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 Not under consideration
Created by Guest
Created on Nov 3, 2022

To increase the limit of 16 character names (SNODEs) in the Secure+

Good morning

Most of our transactions used in our transmission central services must be secured. So we need to use Secure+. Most of our transactions are using DNS value so the CDZ limit of 16 character defined in the network map is affecting us.

Most of our DNSs are larger than 16 chars.

Without Secure+, we can work using larger DNS (netmap is not validated) but with secure+ we can't work using larger DNS (>16char)


What is your industry? Banking
How will this idea be used?

If this limit increases its value (for example 72 positions) plus with the increase of netmap limit CDnodename (https://watsonsupplychain.ideas.ibm.com/ideas/CONDIRECTZ-I-59) will permit to use Secure+ in a standar installation with DNS with more than 16 chars.

  • Admin
    VIJAY CHOUGULE
    Dec 22, 2022

    Hi,

    Thanks for your response. The risk arises from the fact that the workflows in the application are modelled based on the current characeter limitation which is essentially a standard across all OSs. Moreover our customers have historical data that is retained below that limit and we need to consider those scenarios as well while changing the limits. Also we havent seen enough customers requesting this however we will keep an eye on this idea to see of others vote or comment on the same to revisit this in future.


    Thanks,

    Vijay Chougule

    Product Management.

  • Guest
    Dec 19, 2022

    We disagree with this argument.

    We don't understand which is the technial reason to cause significant impact to your broader customer base.

    Netmap entries are meant to be unique identifiers for each partner a node interacts with. --> OK

    The 16 character limit has been standardized across all OSs and trying to extend these fields would require coordination across all OSs and versions that are supported. --> OK

    This would introduce significant risk that far outweighs the benefits that may come from it. --> We don't understand why increasing the size of the items in the netmap can increase the risks


    In a real world, the DNS are larger than 16 chars. This happens in our installation and in many other installations that we know. CD is forcing, AGAIN, customers to develop an external translation table with the relation of large DNS (real) & short DNS (used in netmap). This is not scalable.




  • 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 will not be able to accept this request as it would cause significant impact to our broader customer base.


    Netmap entries are meant to be unique identifiers for each partner a node interacts with. The 16 character limit has been standardized across all OSs and trying to extend these fields would require coordination across all OSs and versions that are supported. This would introduce significant risk that far outweighs the benefits that may come from it. Because of that I must decline this request, but I would encourage you to use the tool to suggest new ideas that may come up.


    Sincerely,

    Chris Sanders

    Connect:Direct Product Manager

2 MERGED

To increase the limit of 16 character names (SNODEs) in the network map

Merged
Good morning Most of our transactions used in our transmission central services are using DNS value so the CDZ limit of 16 character defined in the network map is affecting us. Most of our DNSs are larger than 16 chars. So we need to do an extrapo...
3 months ago in Sterling Connect:Direct for Z/OS 0 Not under consideration