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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
I’d like to request an enhancement to IBM i SQL Services to improve flexibility when passing multiple values to parameters that accept lists.
Currently, the following syntax does not work:
table(qsys2.active_job_info(subsystem_list_filter=>'QINTER, QBATCH, QCTL, qhttpsvr'))
However, the following DOES work:
table(qsys2.active_job_info(subsystem_list_filter=>'QINTER,QBATCH,QCTL,QHTTPSVR'))
While this behavior is consistent across IBM SQL Services, it creates unnecessary friction for users. The rigid formatting requirements force developers and end users to conform to specific input styles, leading to frequent errors and frustration.
Proposed Enhancement:
IBM SQL Services should be enhanced to accept multiple input styles for list-based parameters, including:
• Ignoring case sensitivity for names and reserved values. (this one applies to all parameters, not just multiple list entries)
• Allowing values to be separated by commas with or without spaces.
Why This Matters:
One of the key benefits of IBM SQL Services is to simplify access to system information—particularly as an alternative to calling IBM APIs directly, which are already known for their strict and rigid parameter handling. However, the current SQL function restrictions closely mirror these API limitations, negating much of the usability advantage SQL Services are supposed to provide.
As a result, many users are reverting back to CL commands because:
If SQL Services are to be the preferred method for accessing system data, they must be at least "nearly as user-friendly" as CL commands. By making input handling more flexible, IBM can improve adoption and ease of use, reducing user frustration and support overhead.
We believe this enhancement will significantly improve usability and encourage broader adoption of IBM i SQL Services. Thank you for your consideration.
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Db2 for i development team
IBM Power Systems Development
Thanks for the comment. You actually have case-sensitive SBSD names on your system? That's new to me... but aside from that, the way I do it in my own function is to check if the "name" is enclosed in double-quotes (e.g., "Q38subsys") and if it is, I avoid converting to uppercase. IBM could easily do the same.
I second this request, at least for the spaces, but I am not sure about the case sensitivity. In the subsystem_list_filter I can see the value of it, but for things dealing with the IFS I would prefer it still would be case sensitivity