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.
firstname.lastname@example.org - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for submitting this RFE. While we agree that this function would be nice to have, the joblog would have to be produced in order to search it since the interactive job log is not a searchable file. Each message is retrieved from the message file as it is put to the display. The internal job message queue only contains the message ID and replacement text data.
The suggestion from the RFE community to use the JOBLOG_INFO table function is an excellent alternative.
When called from ACS, the message text is converted to the job CCSID so the joblog can be easily searched using this interface.
Would the JOBLOG_INFO table function help?
To me, the format is a little awkward, but it has been helpful. Not exactly what you are looking for, but it does avoid the "Print/Open-spool-file/Search-spool-file" process
SELECT MESSAGE_TEXT FROM TABLE(QSYS2.JOBLOG_INFO('817029/QUSER/QPADEV0004')) A
WHERE A.MESSAGE_TEXT LIKE '%Disabled%'
Also has the advantage of being able to use it with your own job, as "('*')"
There is a similar table function for the history log. Example:
SELECT * FROM TABLE(QSYS2.HISTORY_LOG_INFO(CURRENT TIMESTAMP - 1 DAY)) X
The same goes for DSPLOG.
Yes that would be very good indeed. Or at least a function key in DSPJOBLOG - F21 Print Joblog. Now you need to quit DSPJOBLOG and remember the full job name and re-run DSPJOBLOG (full job name) *PRINT. Cumbersome.