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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Please finish/complete the integration of long SQL names into Db2 for i
When Long SQL Names are used, you can only rename those object using the SQL RENAME statement. However, RENAME supports only TABLEs, VIEWs, and INDEXes. Which means *FILE objects only. Sequences, Variables, Functions, Procedures, and the myriad other SQL "types" are not supported.
When using Long SQL Names, you can't extract the object name via any interface exception the OBJECT_STATISTICS table function. The QDBRTVSN API only works with *FILE and *LIB objects.
When using Long SQL Names, you can't move an object, unless you specify the related System Object Name, which means using the OBJECT_STATISTICS table function first, obtain the short, system object names, then using those often obscure names with the MOVOBJ or similar interface.
My recommended solution is to add the long name attribute to the OIR and build one of those internal indexes over it for fast access.
But unlike the current SQL implementation, whatever API or interface you provide to support the long names, please make them case-insensitive unless they are "double quoted".
Do not place IBM confidential, company confidential, or personal information into any field.