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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
As for using the SQL VIEW... messages file and message ID access is supposed to be extremely fast... reading the 30th message in a message file with a view that builds across all 20,000+ messages in the file first, and then omits the 19999 you don't want isn't efficient.
The view can be used for certain global things, but not for message ID retrieval.
The reason it IS needed is because of the "Retrieve Option" parameter.
If I specify *NEXT, or *FIRST, and use format RTVM0100 or RTVM0200 I do NOT know what message information has been returned.
Optional Parameter Group
Retrieve option
INPUT; CHAR(10)
If this parameter is not used, it is defaulted to *MSGID. The following options are allowed:
*MSGID Retrieve the message description specified by the message ID parameter. This is the default value of this parameter.
*NEXT Retrieve the next message description in the message file that is after the message description specified on the message ID parameter.
*FIRST Retrieve the first message description of the message file. Note that if *FIRST is specified for this parameter, the message ID parameter is ignored.
The MESSAGE_FILE_DATA view will let you pick and choose which fields you want returned from the message file more easily than the APIs.
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzajq/rzajqviewmessagefiledata.htm
It's unlikely that we would add an additional format to the API just to add a field that is already available on another format, without a good reason, such as performance. While usability of the API is a valid reason, it's not likely to make the cut when we have to prioritize this request against other requests for enablement of features or function that does not already exist on any API or SQL service.