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.
Blocking Db2 connections to reduce the DSNL030I message flooding.
Often times, an invalid password or a revoked ID results in DSNL030I message. Some web based applications does not have error handling for this message and keeps on trying to connect to Db2 sometimes at a rate of hundreds per second. This flood of DSNL030I / ICH408I message fills up the ECSA. There is also a risk in the Db2 MSTR address space to reach maximum number of lines and then crashing. Even an invalid RACF ID can result in DSNL030I message. This idea is to either provide a way to suppress the repeated messages or be able to block certain IP addresses at the z/OS or network level.
The existing functionality only accespts IP address. Further filtering it to a specific AUTHID is needed. Multiple application connections using different IDs also use the same IP address. Therefore it will not be nice to block the whole server.
Do not place IBM confidential, company confidential, or personal information into any field.