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 (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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Is a defect
Created by Guest
Created on May 28, 2020

Verify ControllerWorkflow is functioning properly in 6.0.2.1 with regard to force terminate

ControllerWorkflow.sh doesn't seem to be force terminating a BP when it is in a halting or active state when the BP shows it is in wait queue.

What is your industry? Automotive
How will this idea be used?

Previous versions of SI has been able to force terminate a BP. This version, even though the return code comes back as zero, doesn't seem to be able to force terminate.

  • Guest
    Reply
    |
    Mar 13, 2023

    This issue still exists in 6.1.0.3 version. Is there any fix for this?

  • Guest
    Reply
    |
    May 29, 2020

    Thank you for participating in the request for enhancement community. This request should be treated as a defect. Please open a support ticket for this, any change in behavior needs to be documented. If a feature was working before, and it is no longer, that is a defect.