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.
Thank you!!!
This change is delivered in release 7.5.
IBM Power Systems Development
Our product, 5770RD1, Content Manager OnDemand for i, makes extensive use of qshell. Multiple customers have complained over the years about the excessive production of unnecessary joblogs when using our product. Implementation of this RFE will be welcomed by our user community.
Changing status to 'Planned for Future Release.'
Reopening this RFE after doing additional research on the CPF2523 message. More testing is needed to avoid any regression errors, but I think we may have a solution. We would still produce the joblog when using DSPJOBLOG OUTPUT(*PRINT) since the user is explicitly requesting a joblog in that case, but we would not produce the empty joblogs during job termination. I believe this was the original intention of the CPF2523, but a change to fix a defect may have changed the behavior unintentionally.
Thank you for the information provided. There was a recent issue described in this support document that I thought you may be experiencing: https://www.ibm.com/support/pages/node/638197.
This use case could easily be avoided by using the more strategic SSH Terminal interface provided by IBM I Access Client Solutions. The qshell interpreter runs in a prestart job which by default will use the QDFTSVR job description, which do not produce job logs.
The 5250 interface runs qsh commands in a batch immediate by default, which copies its job attributes from the parent job, so the logging level is the same as the parent job. You could run the commands in a prestart job that uses a job description with a different logging level. It would be incompatible to change the logging level to only log when it thinks you want the joblog. Some users may be confused by this if they are trying to determine whether the logging level is set correctly when they DO want to produce a joblog.
No, those PTFs do not apply. This is very simple to reproduce.
I did this test on IBM i 7.4:
Sign on to an interactive session and issue a CHGJOB LOG(4 0 *SECLVL).
Start QShell.
Do 10 ls commands.
Exit QShell and do a WRKSPLF. You'll have 10 job logs with user data QP0ZSPWT with message CPF2524 - "No job log information".
This is a trivial example, but the same thing applies to more complex situations.
I simply want the system to no longer create these job logs for QShell work when the job description is set to (4 0 *SECLVL).
These QP0ZSPWT jobs do not have the CPF1124 and CPF1164 messages logged to them. When there are no other messages, please do not generate a job log.
Many clients have job descriptions set up with LOG(4 0 *SECLVL) and end up with problems with too many jobs if they use QShell without realizing the ramifications of the LOG setting. Protect the system and the client by eliminating this behavior.
This sounds related to a recent CPS.
Do the following PTF's eliminate the problem?
R710 SI73750
R720 SI73751
I don't see how the use of -s on the system command will help. CL commands are not being used; shell commands are used.
If the initial interactive job has LOG(4 0 *SECLVL), a job log is created with "no job log" for every one of these QP0ZSPWP/QP0ZSPWT jobs.
For example, simply doing an 'ls' command in QShell will give you one of these empty joblogs.
Dawn
The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed. There is a workaround available details in the link below (use -s instead of -K)
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzahz/rzahzsystem.htm
Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.
To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT
Therese Eaton – CEAC Program Manager, IBM