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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Dear Todd,
Thank you for raising this RFE and for clearly explaining the status‑reporting discrepancy observed with Connect:Direct (CD) transmissions. We appreciate you grounding this request in a real operational need and in comparison with other protocols.
This request highlights an inconsistency in how transmission status is reflected across protocols. Today, CD transmissions are marked green as soon as a file is written to the file system, even though the CD session may still be in progress. In contrast, SFTP and other protocols only turn green once the session is fully completed. This can create a misleading signal, masking CD delays or failures and reducing operational visibility.
Aligning CD status behavior so that it remains yellow until the CD session completes successfully would provide a more accurate reflection of end‑to‑end data delivery, improve troubleshooting, and bring CD status semantics in line with other communication protocols.
Questions :
To ensure correct interpretation and implementation, the PM should clarify:
Success definition
What specific event should mark CD transmission as “complete”?
(session close, final ACK, partner confirmation, etc.)
Failure visibility
In the event of a CD failure after file write, how should the status transition (e.g., yellow → red)?
User impact
Are there existing operational workflows or alerts that rely on the current “green on file write” behavior?
Scope
Should this behavior change apply to all CD transfers globally, or be configurable per partner or connection?
Consistency expectations
Are there any protocol‑specific nuances where CD should intentionally behave differently from SFTP, or is full alignment desired?
These details will help ensure the status logic accurately reflects business expectations while avoiding unintended operational side effects.
Thanks again for submitting this thoughtful enhancement request. Improving consistency and visibility across protocols is essential for operational confidence, and your feedback helps drive that improvement.
Manoj Panda
Senior Product Manager
IBM Sterling