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

DCB Information is missing in the parameters passed through the Process Data for CDSA Runtask

We have a requirement for additional parameters to be passed to the B2B Integrator CDSA through the Runtask exit to the Runtask Business Process script. Previously, parameters have been added to the data passed from the inbound Connect:Direct session to the Runtask exit based on RFEs from other customers. The information currently missing from the parameters passed is the DCB information which is required for Connect:Direct zOS file transfers. This data is visible in the logs as shown in the sample below as CopyHandler.finishData. All available data from the Connect:Direct process should be passed to the Runtask process. Please add this DCB information to the data passed.

[2024-06-18 10:40:58.046] DEBUG [Thread-10124/11353] CopyHandler.finishData(true, recordlength=80,blocksize=27920,recordformat=FB,datasetorganization=PO) - Session: XXXX_GTR_CD_SVR_APT1_EXTNL-SFG_CDSERVER_ADAPTER_node1S03770952132L7923 () DocId: 9211641902bcb10acnode1

In addition, there may be a related issue with the passing of the SenderSessionID details (reference PMR TS016445826). This may be a bug. This parameter is passed if a password is provided with the User ID in the Connect:Direct process, but that is often not the case in Connect:Direct usage. If the password is absent no SenderSessionID which includes the user ID information is passed and this is required for correct processing in Connect:Direct.

All of the above should also be available for the CDSA Runjob exit but Runtask is the priority.

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

We need the DCB information from the Runtask, we see that the data is written to the log but not present in the Process Data

  • Admin
    Mark Allen
    Reply
    |
    Aug 16, 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.


    PM and Dev have done a thorough investigation on this RFE and determined that it cannot be accomplished in the short or medium-term. To make this change, the programming contract between the C:D protocol engine and B2Bi will require a redesign between these components. A change this large cannot be delivered in an ifix or fixpack and would require a major version change, mod level or higher.


    This comes with significant risks to existing C:D customers who rely on the current behaviour of the B2Bi CDSA. An extensive testing cycle with mainframe environments would be required, adding additional time and scope to this request as any changes need to be backwards compatible.


    Additionally, this work would come at the expense of other major features currently in-progress that would be of benefit to DTCC and other customers -- TLS 1.3, SHA2 & FIPS 140-3 support.


    If you have any additional feedback, thoughts or ideas, or if there is anything else I can do, please do not hesitate to reply to this message to continue the conversation.

  • Guest
    Reply
    |
    Jul 17, 2024

    After further review, we find that the DCB information that is shown in the CDSA logs is the DCB from the source file.  For the application to work properly, we need the DCB for the target file which is described in the COPY step in the Connect Direct process.  

    1 reply
  • Admin
    Mark Allen
    Reply
    |
    Jul 3, 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.