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 Submitted
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