Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Future consideration
Workspace Spectrum LSF
Components Scheduling
Created by Guest
Created on Apr 28, 2025

GSLA Resource Loaning - Add the ability to loan to specific users or projects

When a GSLA resource pool is defined for a specific type of workload, it is not practical or desirable to loan to just any other type of job profile. The work-a-round today is to include a resource limit definition to prevent this from occurring. This adds additional overhead to the scheduling process and can be detrimental to the service itself if the host pool is larger than a few hundred servers.

Add a BORROWER policy to the LOAN_POLICIES definitions to limit who can borrow from the particular resource pool.

The BORROWER can be a PROJECT, FAIRSHARE_GROUP, or list of USERS. In the event of multiple BORROWERS, the solution should allow for a percentage of the loan pool to be assigned to each BORROWER. (As depicted in Idea SPCLSF-I-716)

Wildcard capability should be an option for the PROJECT borrower setting, since the PROJECT code could be constructed with a common prefix followed by multiple suffix values.

By including this BORROWER capability, the additional limit can be eliminated and the borrower can be evaluated as part of the loaning algorithm for better scheduler efficiency and control.

Needed By Yesterday (Let's go already!)
  • Guest
    Jul 25, 2025

    One of the things that we really wanted was to limit the amount of loaning in a pool by the Service Class (Owner of the allocation).  So, say a team owned 5k cores that 500TB of memory, they only wanted to allow 2k cores and 200TB of memory to be loan-able from their allocation.  The whole loan policy is a global value in the pool and not configurable by Service Class basically.  The idea of who can borrow layers nicely in to that concept.

    On the wildcard bit, having that be a regex is critical IMHO.

  • Admin
    Bill McMillan
    Jun 9, 2025

    This is something we may consider in the future based on community voting.