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
We have a request for adding a property to the DnqMsifInput node that will control how many errors the node will report. Errors in this context is number of Reason entries in the ReasonList.
We are using the DnqMsifInput to validate MX messages, and we have seen messages with as many a 634 errors reported. The DnqMsifInput node spends significant amount of time and resources (cpu, storage) reporting all these errors. And observed response times between 4 and 23 seconds (clock time). Which would call for a high number of multiple parallel running instances of the msgflow.
I suggest the addition of a property that allows for configuring the node to skip further checking after detecting the requested number of error(s) as per the property.
We use the DnqMsifInput node to provide a service for our back office systems, letting these having messages validated before the actual sending. This allows our back office systems to correct messages before sending, when required.
Suggestions for the the property (either will work)
Property name : "Number of errors to report" Value range : 0 - 99999 , default is 99999
Property name : "Max numbers of entries in the Reasonlist" Value range : 0 - 99999 , default is 99999
If easier then maybe this less sophisticated alternative Property name : "Report all errors" Value range : True False , default True
We are using the DnqMsifInput to validate MX messages, and we have seen messages with as many a 634 errors reported. This is an extreme case, but we need a method of controlling the time and resources spent on validation messages, even extreme messages. This property will be the only measure to protect the validation msgflow from extreme messages.
A property to control the amount of resources spent in DnqMsifInput will also reduce the response time , and will be much valued. The sooner the better.
Provided is a trace from a trace node. I believe the trace will also show the messages being validated.
Do not place IBM confidential, company confidential, or personal information into any field.