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 Jun 27, 2019

Ability to rename a windows server nodename or add an additional "alias" node name of sorts

In our environment we came up with the decision to use an alias node naming convention, where our customers create an alias address for a Connect Direct server i.e We take the alias-name part and use that as the Connect Direct node name. When the customers’ servers are upgraded, we install Connect Direct on the new replacement server and give it the same alias name as the server it is replacing, and when the customer’s server goes live we will repoint the alias address from the old server to the new server. We did this in order to ensure the vast number of our users no longer have to worry about having to change the node names in their .cdp files, JCL, and bin files when they move to their new server.

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

Connect Direct Application support staff will be able to setup an automated puppet install package for deployment to customer's new servers. Post install, app support staff will either be able to rename node name or add second/alias node name on server. App support staff will configure user setup. User import existing scripts, cdps, bin files and run jobs on normal schedule.

  • Admin
    Chris Sanders
    Jul 15, 2019

    Thank you for opening this enhancement request with IBM. I have reviewed it thoroughly with my team. Unfortunately we will need to decline the request due to the technical impact that it would have. The node name that is chosen during installation is used in multiple areas such as setting up the service that C:D runs under, in the DB, registry, statistics, and other areas. Trying to change these after installation has a potential to cause unnecessary defects so we can't justify making this change.

    I did want to make sure that you are aware that the nodename can bet set by using the Custom installation option however. The default nodename is the hostname of the machine, but by chosing the custom option you can set it to whatever you would like. This should give you the opportunity to proactivly set the nodename to whatever you'd like it to be when the server is deployed.

    Thank you for opening this request and I'm sorry that I couldn't accept it. Please don't hesitate to use the tool again in the future should you have other ideas that we could explore.


    Chris Sanders

    Connect:Direct Offering Manager