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
Provide access to "extraction program" used by DSPLOG and QMHOLHST API for Developer use
The QMHOLHST API is fine for simple selection and use but it not only omits a few pieces of the QHST log (such as from program and stmt nbr) it also severely limits the number of jobs that may be used to restrict the results. (currently 5) and the number of message ID to a less restrictive but still restrictive 200.
Scenario: I enumerate the list of qualified "Last Submitted Job" IDs from the Job Scheduler and then try to list the messages related to those jobs, including the start/end job messages. So I go after them in QHST. The QMHOLHST works fine when there are only 5 or fewer jobs, but once we get 6 or more, it requires the use of an INNER JOIN to the job scheduler table.
The issue there is without limiting the messages being returned by QMHOLHST or the IBM-supplied HISTORY_LOG table function to only our Job Schduler Jobs, those interfaces have to go "back in time" and build the list of all messages in QHST (unless we limit the time frame which may not be known or desired) and then throw away what we don't want via a JOIN or WHERE clause.
If the interface that extracts the the QHST LOG content and puts it into a usable format were published, we could call it ourselves and have better response time.
Do not place IBM confidential, company confidential, or personal information into any field.