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 Submitted
Workspace Spectrum LSF
Components Administration
Created by Guest
Created on Dec 10, 2025

Request for configuration parameter “HNAME_MAX_NUM” to limit the number of hname conditions in RES_REQ.

In production environment, automated scripts (for example, Synopsys CDPL) generate very long RES_REQ strings with thousands of (hname!='hostX') conditions in the select clause, which has led to mbatchd/mbschd performance degradation and scheduling slowdowns or stalls.

Today, LSF has no built‑in parameter to limit RES_REQ length or the number of hname conditions. Administrators must rely on an esub script that parses the select string, counts hname==/!=, and aborts the job when the count exceeds a threshold.​
This works technically but requires per‑cluster deployment and does not provide a product‑level safeguard.

LSF already provides parameters like ATTR_MAX_NUM to limit the number of host attributes and protect cluster performance. In the same spirit, we would like to request a new configuration parameter as follows:​
Name: HNAME_MAX_NUM
Location: lsf.conf (cluster level) and/or lsb.queues (queue level)
Value: positive integer; 0 or undefined means “no limit”

Expected behavior:
LSF counts all hname== and hname!= conditions in the select section of RES_REQ and rejects submissions that exceed HNAME_MAX_NUM, with a clear error message.
A cluster‑level default may be overridden per queue, so stricter limits can be applied only to specific queues if needed.

Needed By Not sure -- Just thought it was cool