Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Not under consideration
Workspace IBM i
Created by Guest
Created on Feb 23, 2024

Change ADDWLCGRP "Add Workload Group" to set the processor limit < 1,0

Our customers are using LPARs with less than one CPU assigned. To reduce the impact of ad-hoc queries (e.g. via ODBC) we need to set a CPU limit of the ODBC subsystem. Currently with a workload group we can only set a limit to a whole CPU.

But we need to set a lower limit like 0,2 CPU for the ODBC subsystem. Can the workload group be changed so that a value lower than one CPU can be assigned?

Idea priority Medium
  • Guest
    Mar 11, 2024

    If I have understood your idea correctly, you can achieve what you want (limiting the maximum impact of ad-hoc ODBC jobs) by using subsystem routing. Whilst this does not place a cap on the processor resource, it does allow you to control the resources associated with these jobs as well as their priority on the system.

    Please take a look at the article below, it gives a good explanation of how to set this up.

    I hope this helps.

    Steve Bradshaw
    IBM Champion, Member of CEAC, TD or and Friendly Techie at

  • Guest
    Mar 5, 2024
    We've had this request before, and while I understand the use case and the desire for this function, the current WLC group architecture was never designed to support limits less than a full core. This would require a complete redesign of WLC group architecture from top to bottom. The WLC group design point was to support sub-capacity licensing, and workload management was never really part of the intended use, although it has been used successfully (in some capacity) for this use.

    I am declining at this time because it would require tradeoffs which I do not envision as possible due to its size and complexity in order to fit it into our development plans.

    IBM Power Systems Development