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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Add System Acknowledgment status generated off an outbound communication protocol result
In line with the current System Acknowledgment solution around sending a message back for an outbound transaction with the translation status (SYSACK1) and processing a functional Acknowledgement back from a trading partner for the corresponding outbound message (SYSACK2), I would like to add an additional acknowledgment determining the status of an outbound communication session (SYSACK 1.5). This acknowledgment would reference the message(s) acknowledged in the SYSACK1 by checking the down stream communication steps in the process. Based on the result of the comm step, and additional message could be derived to send back similiar information that is sent in the SYSACK 1 along with the communication status and any relevant information about the communication session. For example, for an AS2 session, utlize the results in the MDN to provide the status and actually send back the MDN. For an ftp/sFTP session, utlize the communication logs to send back the results of the session and include the log as well. Other protocols can follow the same process.
Do not place IBM confidential, company confidential, or personal information into any field.