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 will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it.
*LAST would be very nice indeed but what about *ALL ?
That would be like a SQL union that can read thru all members.
Thank you for your input. We will use that as we continue to evaluate this request. IBM will provide a response after evaluation is complete.
Thank you very much:
From a functional perspective, my preferred option is that the *LAST be evaluated at query time, so each time the alias is used, it will be answering with rows on the actual last member at query time.
If that is not possible (or impractical, or have a high impact on performance), I think is good enough to implement a version where *LAST be evaluated at CREATE ALIAS execution time, and, if users need to refresh the definition, they can execute a CREATE OR REPLACE ALIAS... which in any case is easier than creating Stored Procedures that check the last member of a file to create a new alias or creating stored procedures with an OVRDBF.
If the CREATE ALIAS statement were to support a value of *LAST, is the expectation that the alias is created with the current *LAST member, or should the value of *LAST get determined each time the alias is used in another SQL statement?
IBM has received the requirement and is evaluating it. IBM will provide a response after evaluation is complete.