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
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,
Post an idea
Upvote ideas that matter most to you
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 a notification 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.
If you encounter any issues accessing the Ideas portal, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Provide topic or subscribtion option to duplicate msg id
When messages are published to a topic, either via a direct publish, or by putting the messages to a qalias with targtype(topic) a message id is assigned. When the message is delivered to any subscriber, a different msg id appears on the message. The message delivered is therefore not identical in all respects to the message sent.
Please provide an option to allow exact duplicates of messages to be delivered.
This could be implemented as a topic option (duplicate msgid) or as a subscriber option (receive duplicate msgid).
Imagine an application which puts requests messages and waits for the response to be returned to a replytoq.
The organization would like to be able to collect a copy of all messages sent by the application (say for audit purposes).
The queue is deleted, and a qalias defined which has targtype(topic). The topic is defined, and 2 subscriptions are created. One subscription puts the message to the original target, and the second one puts it to an audit queue.
At the moment, this scenario cannot be implemented without changing the applications, because the server application which receives the request will get a message with a different msgid than that sent. If it follows the default reply mechanism (copy msgid to correlid) and the requesting application also uses this convention, the reply will not be found because the correlid will be wrong.
With an option to preserve message ids, this use case becomes feasible and useful.
Option to deliver Publishers Useridentifier in MQMD to Subscriber
Using MQ PublishSubscribe a message delivered to a subscribers queue contains the subscribers useridentifier per default.We have an application where the subscriber needs to know who has published a message. This is not reliable possible when the ...
We have a program that fans multiple copies of messages to multiple queues which are identified in a namelist. We use this extensively across our enterprise for migration purposes as well as just providing a message to several different Program O...
Do not place IBM confidential, company confidential, or personal information into any field.