Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Sep 13, 2018

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.

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
    Sep 17, 2018

    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.



    Chris Sanders

    Connect:Express Offering Manager.