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
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.
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.)
Do not place IBM confidential, company confidential, or personal information into any field.