This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 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
Specific links you will want to bookmark for future use
filter specific IDAA messages from being delivered to DB2.
All IDAA messages, once delivered to DB2, are wrapped in a DSNX881I message ID and displayed within DB2 and on the z/OS logs. In our case there was a VERY lengthy message of type /W3005/ which is delivered to us no less than 15 times a day for each of our accelerators (we have 8). We have automation that intercepts every DSNX881I message and sends it via email to the team responsible for IDAA support. Sometimes these messages have to do with tables that have gone into an error state for replication, or they may have to do with high replication latency. We find THESE messages very important, and we take action when we see them. However the /W3005/ message is useless for us. We have been advised in IBM case TS013890749 that we can ignore this message. But this message will still appear in DB2 and in our logs. It is very lengthy and it generates a lot of 'noise' in the logs. We would much prefer to not receive such messages rather than to customize our automation to send SOME messages in DSNX881I but not send others. Can a means be developed to prevent specific messages from being delivered to DB2?
Do not place IBM confidential, company confidential, or personal information into any field.