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 Apr 29, 2024

How to pass SACCT and PACCT details to remote CD Node using CDServer CopyTo Service in sterling integrator?

We have a requirement to PASS the SACCT and PACCT details to remote CD node from sterling integrator. We do not find any relavent fields in the CopyTo service in sterling integrtor to handle these values. Can you please provide the tags we need to use in the service to pass this information during the CopyTo step?

  • Admin
    Mark Allen
    Reply
    |
    Jun 14, 2024

    Thank you for taking the time to provide your ideas to IBM. We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.

    IBM has evaluated the request and has determined that it cannot be implemented at this time or does not align with our current strategy or roadmap.


    The RFE is asking for the CDSA adapter to behave very differently than the way it was designed to. The issue is that there no framework in the B2Bi CDSA adapter to add the custom behavior being requested. This functionality exists in Z systems, but not in any other C:D platform.

    The work to change the CDSA adapter to fit this use case would be extremely large and is not valuable to the broader market. If we accepted this change, it would uproot our roadmaps into 2025 and have a delivery date well past what DTCC is looking for.


    A workaround option involving setting up additional C:D nodes to pass on these details to remote C:D nodes has been provided to DTCC & CoE.


    We may look to reconsider this request in the future. We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.


    Please note: IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion.

  • Guest
    Reply
    |
    May 17, 2024

    A Connect Direct Process script has two levels of scope.  There are parameters that are at the scope of the full Process and others that are specific to steps withing the Process script.  The SACCNT and PACCNT parameters are at the Process scope and not specific to the CopyTo service.  Adding the SACCNT and PACCNT parameters to the Connect Direct services in B2Bi may actually be best done at the scope of the process which might be the BeginSession service.  This would involve adding these as parameters to the BeginSession service which would be passed to the remote Connect Direct server at the appropriate places in the command stream.  In addition, any other Process scope parameters could be added in the same manner allowing B2Bi to more closely appear as a Connect Direct server when exchanging data with an actual Connect:Direct server. For any platform specific parameters, I would suggest making B2Bi look like a CDU server, but other options might be considered. 

    1 reply
  • Admin
    Mark Allen
    Reply
    |
    May 8, 2024

    Thank you for taking the time to provide your ideas to IBM. We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.

    We are currently reviewing this request with our technical team and will update the status once our analysis is complete.