It really is tough to go back and review joblogs. And trying to automate
that would be interesting. For example, you have a CL program that does
crtdupobj otherlib/thatfile to mylib/workfile
That first dltf is just a cleanup. And the programmer didn't make the
effort to clean the joblog of the escape message.
This is really quite common.
Now, in some other program this may be a real concern.
You end up having to train the monitoring tool.
We use GO CLEANUP to automatically purge joblogs and whatnot after so many
We also do NOT spool joblogs at all. We used system value QLOGOUTPUT to
just make them *PND instead. Keeps the users from going crazy since these
no longer show up on WRKSPLF. If I need a 'spool' copy I simply do a
DSPJOBLOG JOB(...) OUTPUT(*PRINT)
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact