IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

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,
1. Post an idea
2. Upvote ideas that matter most to you
3. 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 notifications 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.

Purging notification records at run-time

With current Windows Connect:Express versions, when notifications are enabled, notification records are added at run-time in the local database, even when they are fully processed (notifications messages sent), and they remain there, possibly very numerous, until the monitor is restarted. It is a major issue if the monitor is rarely restarted...

We moreover noticed that past a certain amount of records, all file transfer processes take more time and more CPU.
Enabling notification records purge at monitor startup then becomes mandatory, but as records are deleted one by one, the purge process may last a very long time before the monitor's availability for transfers.

So it is very annoying and the purge process should be available at run-time,
* at least as a scheduled internal task (as it is done for requests)
* and if possible, manually triggerable by admin user.

  • Guest
  • Sep 13 2018
  • Future consideration
What is your industry? Banking
How will this idea be used?

When notifications are enabled (needed for us for file transfer statistics processes), without notification records purge, there is a time when monitor becomes unusable with transfers abnormally long and random delays.

  • Admin
    Chris Sanders commented
    17 Sep, 2018 12:57pm

    Thank you for your interest in this enhancement.  I've reviewed this request with my development team and we are all in agreement that this would be w worthwhile enhancement.  I will accept this request as an uncommitted candidate and we will look to add it to the Connect:Express roadmap moving forward.

     

    Sincerely,

    Chris Sanders

    Connect:Express Offering Manager.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.