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
Eliminate QZSHSH, QP0ZSPWP/T Job Logs with "No Job Log"
When a user has their job set with a logging level to generate a job log (e.g., LOG(4 0 *SECLVL)), then uses QShell, there is a jog log generated for every QShell command, with the job log having a single message, CPF2523, "No job log information."
While the logging level specifies that a job log is to be created, it is no longer good for the system to generate job logs for these jobs spawned by QShell.
Consider a large system, using QShell in a batch mode to remove unnecessary files from the IFS. There can be a potentially very large number of job logs created, just stating there is no job log.
Given the increasing use of Open Source, the IFS, and QShell, when the QZSHSH, QP0ZSPWP/T jobs end with no job log, let them end with no job log. That is, change the behavior to eliminate the job log with CPF2523 message.
A client had a weekly job to clean up the IFS. The job was submitted to batch with (2 40 *SECLVL) and used QShell in batch mode to remove files from the IFS. Because of the logging level, each week they would generate nearly 60,000 job logs, all of which were job logs with just the CP2523 message.
The client did not realize this was the cause of the huge number of job logs on this system; they had tried all sorts of approaches to clean up job logs, but continued to struggle with the issue. It took expert assistance to identify the problem with their job description that caused these job logs from their IFS cleanup.
This is a waste of system resources and causes a risk for reaching the maximum number of jobs in the system. (This particular client set their QMAXJOB system value to 970,000 because of job log issues like this!)
Eliminating these job logs would be good for overall system health.
Do not place IBM confidential, company confidential, or personal information into any field.