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 May 20, 2024

We have refresh netmap in Mainframe Connect Direct and its not available in Linux connect direct

We had an issue with connect direct process, In the middle of file transfer client brought down the connect direct in primary server and brought up in the secondary. Since the process was interrupted and its keep retrying the primary server. Its not retrying to alternate IP, Its working as designed. 
But in mainframe we have option to refresh Netmap for the processes in wait status. Where we can refresh the netmap for the process and it can retry and process will try primary first and then retry in the alternate IP address. which will resolve the issue.
 

  • Admin
    James Joseph
    Reply
    |
    Jun 13, 2024

    Our proposal is to add new parameter to affect the way alt.comm.outbound works, something like alt.comm.outbound.sticky=[y|n]. The new parameter will default to ‘y’, which is the current behavior as customer describes. However, when alt.comm.outbound.sticky=n, then on restart, an interrupted session will cycle through the comm.info and alt.comm.outbound specifications anew, just as it did for the initial connection attempt. alt.comm.outbound won’t stick to the previously established session in case the session is interrupted and restarted.

    This actually has an advantage over customer’s proposal of adding a refresh from netmap command, in that it will be done automatically, no need for a manual intervention to get processes restarted.


    @Guest


    Thanks,

    Product Management

  • Guest
    Reply
    |
    May 31, 2024

    alt.comm will try to connect the secondary IP, Once the server connected to primary IP and if primary server went down, it will not try connect to secondary. It will always try to the primary.

    So we need an option to refresh netmap for process in TCQ wait status, After the netmap refresh it will
    try to connect primary first and then retry the secondary IP address in alt.comm.

  • Admin
    James Joseph
    Reply
    |
    May 30, 2024

    Prabhu ,Thank you for the raising the RFE.


    Does CD Unix providing an option to alt.comm the outbound that prevents the sticking to one outbound address after the session has been established ? Does the enhancement helps to solve the problem ?


    Thanks,

    James



  • Admin
    James Joseph
    Reply
    |
    May 24, 2024

    Thank you for taking the time to share your ideas to IBM. We truly value our relationship with you and appreciate your efforts and willingness to share details about your experience, your recommendations, and ideas. We will soon review the same in the coming weeks and shall get back with a response.


    Thanks,

    Product Management