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
Order Managment on Cloud INT Server instance to log failing MQ message MSGId and create alert.
Within an OMoC (Order Management on Cloud) environment an INT server instance (IntgName) integrates with the MQ QMGR for reading/writing MQ messages for OMoC integration processing. When the MQGET of a message from an inbound queue fails we see a generic exception in the IntgName instance log, but we are not able to identify the actual message that has failed. The message is no longer on the queue, and so all we know is that there has been message processing in error, but not what the message is. We need to be able to track a message identifier in the IntgName instance log, such as the 'MQ MsgId'. We ideally also need a plugin to this log to create an alert for the message in exception. The first step is to identify what we should use as a unique message identifier, then make sure this is in the exception record.
This will benefit CoC OMoC support, and OMoC customers, and SI teams to trace lost MQ messages.
What is your industry?
How will this idea be used?
This logging will be used by CoC support, customer OMoC support teams, and SI teams to troubleshoot lost MQ messages, that can be anything from a customer order, to a catalogue update.
Do not place IBM confidential, company confidential, or personal information into any field.