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 Not under consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Sep 14, 2021

Integrate SQL Object Name into IBM i Object Description

More and more IBM i object types are being utilized by the SQL environment on IBM i. However, "the database" is supposed to be Integrated, not an add-on on this platform. Therefore when an IBM i object is repurposed as an SQL Object and a LONG name is implemented, that SQL Object Type and SQL Long Object Name should be stored in the object description or OIR itself and not only in an outside catalog system.


Use Case:

When using long names for Tables, Sequences, Functions, Procedures, Indexes, etc. those *FILE (PF and LF), *DTAARA, *SRVPGM, *PGM, etc. may have long names. There is currently no API that provides complete translation of an SQL name to the 10-charcter IBM i name or back again; and QDBRTVSN only works with Files and Library names.
There needs to be this capability and the most efficient way to do that is by adding the 128-byte SQL Name and the 32-Byte SQL Object Type to the Object Description or OIR. By "add to" I mean integrate it so that as we move forward, things like CL commands and APIs, in addition to SQL, can access those names seamlessly. The key would simply be if the name exceeds 10 bytes the Long Name directory would be scanned, otherwise the existing 30-byte directory would be scanned. (Yes we know that object names can be 30-bytes for at least 26 years but aren't implemented.)


Idea priority High
  • Guest
    Nov 29, 2021

    Thank you for submitting this request. We assessed the value vs cost of adding the SQL information to the Object Description (OIR) and decided not
    to implement the changes.

  • Guest
    Oct 14, 2021

    The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed. We understand the thought behind this RFE but in it is current form this RFE seem too broad. Perhaps you could request something more specific to address individual elements of this issue

    Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT

    Therese Eaton – CEAC Program Manager, IBM

  • Guest
    Sep 23, 2021

    Paul, internally the object name is stored in a 30-byte area and has been for decades. They've always only exposed the first 10 bytes. But this is more of an "inside baseball" thing.

  • Guest
    Sep 21, 2021

    The CAAC has reviewed this requirement and recommends that IBM view this as a “nice to have” low priority feature. IBM is staging support over multiple releases, and this should be handled as part of that staging.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Sep 21, 2021

    Completely agree from a design standpoint.
    Identifiers should be in the objects (then used by any catalog if one wants).

  • Guest
    Sep 15, 2021

    Object names of 30 bytes ? Am I missing something ?