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 Delivered
Created by Guest
Created on Nov 6, 2020

Control Center Rule Correlation

Two of the things we utilize Control Center for is SLC notification and processes that do not end successfully. We have some transmissions that are monitored on SLCs that are contractual (sla). We do get an alert if the sla transmission has not started yet or is late. However, if the same sla transmission fails, that comes out on Control Center as a different type of alert due to it being a different event type. Currently it seems to be impossible to build what I call an "error in process" rule that can use rule key SLC name. We would like to somehow correlate the failure of the transmission to it being a contractual transmission so that it will be more apparent to the operator. Our only alternative is to build multiple error in process rules that would contain a list of the contractual transmissions and the rule can be named so that when it comes out, the operator knows that the transmission that failed is contractual.

What is your industry? Non-Industry Specific
How will this idea be used?

This will be used to provide correlation between a contractual transmission that is on a slc and a transmission failure.

  • Admin
  • Guest
    Jul 15, 2021

    Soon this will be possible. Currently, SLC events generated as a result of another event, for example a step end event, perhaps for a file transfer, or a process end event, include that "source" event's event ID and date/time value. We will be adding the message ID and return code values from the source event to the SLC event. This will allow a user to simply add one additional rule to watch for an "SLC was satisfied" event. For example, CSLC037I - Ended as expected. (Rule priority wise, this new rule would be lower than the rule that watches for the SLC events that indicate whatever was supposed to happen, did not, but higher priority than a rule that handles the SLC events that indicate everything worked as it should.) By adding a rule that watches for CSLC037I, along with a criteria that specified the source events return code, one could have an action associated with that rule that informs someone that a transfer did occur when it should, but that it failed.

  • Admin
    Dec 16, 2020

    Thank you for submitting the request for enhancement. We will be reviwing this with development and provide an update shortly.

  • Guest
    Nov 10, 2020