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
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
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.
IBM does not intend to provide a solution to this request at this time, so it is being closed.
As mentioned in a prior update, the performance of the API is optimized to work with names 30 characters or less. Using longer names has a recognized performance cost that we do not plan to address.
The knowledge Center currently explains that long names have some performance ramifications in section
"Effects on database performance when using long object names".
However, the information is not specific enough. The next update of the information will be enhanced as follows:
Long object names are converted internally to system object names when used in SQL statements. This
conversion can have some performance impacts. Names of tables, views, indexes, and aliases that are 30 bytes or less
will generally perform much better names longer than 30 bytes.
Qualify the long object name with a library name, and the conversion to the short name happens at
precompile time. In this case, there is less performance impact when the statement is executed. Otherwise,
the conversion is done at execution time, and has a small performance impact.
Please respond to the question from COMMON Americas Advisory Council (CAAC) in the Comment below.
The CAAC has reviewed this RFE. More information is needed. Please let us know your response to Mark Anderson's comments below. In particular, how did your lengths compare with the best practices recommendation of 30 or fewer characters?
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
For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/
Nancy Uthke-Schmucki - CAAC Program Manager
FYI, for tables whose names are less than 31 bytes, the very first time the API is used for a specific table may take longer, but subsequently, will be quite fast. Furthermore, even though such cases are already quite fast. I am planning to improve the case where names are less than 31 bytes even more.
As long as the length of "long names" for tables are less than 31 bytes, the performance is quite fast and we do not need to access the server job to find the short name. The best practice for performance reasons is to use "long names" whose length is less 31.