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
Post 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 product management 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 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.
Improve quality and trackability of (outgoing) HTTP system log error messages
Currently it is difficult to track a failed http message back to a case, because there are no shared ID between those logs. Best option you have is using the timestamps. Please provide an option to put a HTTP Message ID used in the System Log in the Audit Log or even better a Case ID into the system log.
Please fix APAR 0811 and optimize the content of event 361 to something useful and do not lure users to search for non existing files.
Provide at least the complete HTTP Status Response and not "some error has occured" in event 477. And also put in an ID to relate to an actual message. It is a useless message for an important error.
Provide an option to "find and debug" failed messages while sending. It is difficult to retrieve messages from the EML folder when they are rotating around the cluster. Perhaps you can output them to the filesystem in error cases.
Provide an option to discern regularly archived messages from finally failed http messages, perhaps logging them into a different folder.
Do not place IBM confidential, company confidential, or personal information into any field.