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 26, 2020

One Tracker per LPAR serve all Controller

Due to administrative rules we are forced to run multiple IWSz Systems in parallel on one SYSPLEX. So we have to start tracker STCs for each of our multiple IWSz controllers on every system of the SYSPLEX. As the tracker STCs all do the same work - reporting the status of all the jobs of a system to the controller we would like to just have one tracker STC per LPAR to serve all controller STCs. This would help us especially in migrating IWSz when we have to restart the trackers for multiple systems with a new EQQSSCNMx which occupies CSA below the line multiple times. In this situations we usually have to IPL sysplex wide because we run short of CSA as the CSA storage of the old EQQSSCNMx is not freed after restarting the tracker STCs with the new one. Also a single tracker could save system resources without losing functionality.

Case Number: TS003562543

Idea priority Medium
RFE ID 142642
RFE Product IBM Workload Scheduler (IWS)