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
Created by Guest
Created on Apr 24, 2021

Create a Get Short System Object Name from Long Name API

The QDBRTVSN API has an interesting syntax and is limited to *FILE objects and retrofitted to also work with Libraries.
What is now needed is a new API that works with all Object Types and that converts both the Library and Object names from long to short in one step.
Effectively we need two new APIs: Convert Long to Short Name, and Convert Short to Long Name:

// Convert Long Name to Short System Name

// Convert Short System name to Long Name:

typedef _Packed struct tagLong_t
char Object_Name[128];
char Library_Name[128];
char SQL_Object_Type[32]
} longName_T

typedef _Packed struct tagShort_t
char Object_Name[10];
char Library_Name[10];
char Object_Type[8];
} shortName_T

longName_T longName;
shortName_T shortName;
char objType[8] = "*SRVPGM ";

char longNM[129] = "OBJECT_STATISTICS";
char libName[11] = "QSYS2";

call QLICVTLNS( &shortName, &longName, objType);

Note: The Object Type parameter should be optional and default to "first" or "only" or "any" whatever is standard for such things. meaning it would locate the first object whose long (or short) name matches, regardless of object type.

The returned SQL_OBJECT_TYPE (for Short to Long) operations helps complete the information about the long name.
The returned OBJECT_TYPE for the Long to Short API informs the user what object type is returned. Similar to other APIs that return the library name where and object was located and *LIBL is used (e.g., QUSROBJD)
The Returned Library_Name from both APIs should be returned even if the input library name is blank or *LIBL.

Use Case:

As the number of System Objects that also have Long SQL Names increases (*FILES, *DTAARA, *SRVPGM *PGM today but there may be others already being used) the need to convert those names from Long Name to Short is becoming pervasive and needs to be built into the system.

Idea priority Medium
  • Guest
    Nov 29, 2021

    Sorry that this wasn't processed sooner.
    Database files offer an opportunity to implement a non-SQL API to retrieve the short name, given a long name.
    For other database object types, there isn't the same ability to do better than a call to OBJECT_STATISTICS or to query to the appropriate database catalog.
    Further, for SQL functions and procedures, simply having the long name (routine name) isn't enough detail. Routines can be overloaded, so any service would need to take into account function resolution to provide the complete and correct answer.
    For these reasons, the RFE is being rejected and the recommendation is to query the database catalogs or QSYS2.OBJECT_STATISTICS.

  • Guest
    May 17, 2021

    The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.

    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 @ and the article "The Five Hottest IBM i RFEs Of The Quarter" at

    Therese Eaton – CEAC Program Manager, IBM