IBM Power 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:

Post your ideas

Start by posting ideas and requests to this portal to enhance a Power 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 and add comments to ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Specific link you will want to bookmark for future use

IBM Unified Ideas Portal - https://ideas.ibm.com/ - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Sep 14, 2021

RELATED IDEAS

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 ?

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.