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 (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
  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 (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.

Status Submitted
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Aug 5, 2026

Provide a way to query Db2 for IBM i members

Currently, using OVRDBF to direct SQL statements to a specific database file member is functional, but it is not an ideal solution. It requires an external override that is disconnected from the SQL statement itself, making the code less self-contained and more difficult to understand and maintain.I would like to propose adding a way to specify the member directly within SQL statements wherever a table name is valid. While this would be particularly valuable for SELECT statements and CTEs, it would also benefit statements such as INSERT, UPDATE, DELETE, and MERGE.The current alternative of creating an SQL ALIAS is often inconvenient. It introduces additional object management, requires cleanup of temporary aliases, and becomes especially cumbersome when the member name is determined dynamically at runtime based on user input. In longer or more complex procedures, managing these temporary aliases adds unnecessary complexity.I don't have a specific implementation in mind, but one possibility would be to extend the table reference syntax using something similar to the existing CREATE ALIAS member notation. For example:SELECT * FROM QIWS.QCUSTCDT(JUNE);This approach would make member selection explicit within the SQL statement, eliminate the need for OVRDBF or temporary aliases in many scenarios, and improve the readability and maintainability of SQL code that accesses multiple members.This enhancement would simplify application development, reduce reliance on external overrides, and make SQL code more self-documenting, and easier to maintain.

Idea priority High
  • Guest
    Aug 11, 2026

    Excelente propuesta! Para no crear mas alias! 

  • Guest
    Aug 10, 2026

    I think this is a great idea 

  • Guest
    Aug 10, 2026

    I like this idea, please add

  • Guest
    Aug 9, 2026

    I would very much appreciate if this idea get implemented. Very useful 

  • Guest
    Aug 6, 2026

    I like this idea, because it is cumbersome to use SQL ALAIS.

  • Guest
    Aug 5, 2026

    Excelente propuesta que llevamos pidiendo desde V2