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
Categories IBM i Access Family
Created by Guest
Created on Feb 21, 2020

Add warning in Run SQL Scripts if a join predicate does not reference the joined table

Add the ability to warn the user when they are attempting to run a query that contains a join, and the join predicate does not reference fields from both sides of the join.

select a.field1, b.field2, c.field3
from lib.tablea a
join lib.tableb b on b.anFkField = a.pkField
join lib.tablec c on b.anFkField = a.pkField

In this case, the join predicate on the second join does not reference "c" and is likely a typo - a warning would draw the users attention to this and allow them to quickly cancel the query and correct it.

Use Case:

Occasionally, our developers will write a query with a typo in a join predicate; the result is still valid syntax, but results in a cross join instead of the intended inner join, wasting time and resources.

This problem is magnified when running queries against large tables that are already expected to take minutes to run, because (a) they do not quickly realize the error, and (b) the cross join against these large tables consumes a large amount of temporary storage while processing.

Idea priority Low
  • Guest
    Apr 4, 2022
    Thank you for submitting your Idea to enhance Run SQL Scripts (RSS) in ACS. The Query Supervisor feature for IBM i was provided so that queries could be monitored for excessive resource usage ( Rather than adding support for RSS to check for a specific potential user error, our suggestion is for you to take advantage of features available in Query Supervisor to monitor for excessive resource usage that could be caused by a variety of user errors. Therefore, we have decided to decline this request.

    IBM Power Systems Development
  • Guest
    Jun 25, 2020

    IBM understands this request and will consider it for a future code update, though no commitment is made or implied.

  • Guest
    Mar 10, 2020

    IBM has received this requirement and is evaluating it. A response will be provided when evaluation is complete.