Integration
This is an IBM Automation portal for Integration products. 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
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
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.
Idea / RFE Review. Thank you for taking the time to raise this enhancement request, and apologies for the short delay in providing this response (this idea has now been re-routed from the Cloudpak for Integration team to the App Connect team). We agree this suggestion would improve the product. To clarify the request here, our interpretation is that the requirement here is for either:
a) A single message flow node which is responsible for doing the MQPUT and then an associated MQGET by CorrelId from a corresponding reply queue.
b) A pair of asynchronous message flow nodes, one of which does the MQPUT and then the second the MQGET by CorrelId from a corresponding reply queue.
In both cases, the intention would be to ensure that the correct specific message is brought back in to the message flow, and that the initial message flow thread would not be held up polling for the response. We have discussed a similar architectural pattern in the past whereby an environment variable be used to push a desired CorrelId into the MQInput node in order to drive the MQInput in a dynamic way to meet this same use case ... but the advantage to a dedicated node as per the suggestion would be to maybe enable us to poll for multiple responses at the same time rather than a single response.
Regardless of the detailed scope of design, the suggestion is a good one, therefore the status is updated to Future Consideration.