Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. 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 May 9, 2023

Use the same "Warning" logic , when we delete a Jobstream Object , IWS will alert the user if the jobstream is used in other Jobstreams as a dependency ogic

If you DELETE a "JOB" object from the IWS database and it is included in other Jobstreams , IWS will alert/Stop the delete command because its cross referenced in other Jobstreams. 


If we DELETE a "CPU" object , again IWS will alert/Stop the User from performing this function as other objects may Reference the CPU 


If We DELETE a "Jobstream" IWS Will DELETE the jobstream even if its referenced in other Jobstreams as a dependency.  (change of Behaviour to above)

This was discussed at the UK TUG in IBM , with other IBM/HCL staff present, they also believe that this should follow the same behaviour and Alert/Stop the user of deleting the Jobstream. 



Idea priority High
  • Guest
    Jun 7, 2023

    Good Morning Support,

    We have JUST discovered this also happens when we delete a Dynamic Agent , It also removes that "member" from the Static Pool config. Again when we re-instated the Dynamic Agent a few hours later , the static Pool did not have the member in the Pool. We have had to manually amend the POOL to add the dynamic agent . This should be a WARNING message when we delete a Dynamic Agent.

    Awaiting your response

    Nige Jowett