IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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.

  • Guest
  • Mar 7 2019
  • Not under consideration
What is your industry? Consumer Products
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.

  • Admin
    SUDHIR Balebail commented
    7 Mar, 2019 01:55pm

    This is a very valid requirement for troubleshooting and triaging issues relating to MQ interaction . I will move this to Under consideration. The way in which we choose to resolve this may differe from the ask, but the need is understood, and our effort will be to make sure it is met.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.