If GO CLEANUP isn't active and you don't want to activate it, or you
don't want to wait the required number of days, you can issue a CHGJOB
command for those jobs specifying LOGOUTPUT(*JOBLOGSVR) to force the
joblog to print.
To automate the process for lots of jobs you'll need to write a CL
Program to:
WRKJOB JOB(QRWTSRVR) DUPJOBOPT(*MSG)
A duplicate job named 432575/QUSER/QRWTSRVR was found.
A duplicate job named 432668/QUSER/QRWTSRVR was found.
End of duplicate names.
DSPJOBLOG OUTPUT(*PRINT)
CPYSPLF to capture this to a database file
Read the file, parse the "duplicate job" messages,
then issue CHGJOB LOGOUTPUT(*JOBLOGSVR) for each job
found.
It's somewhat cumbersome (especially parsing a string to find the job
number/user/name), but relatively straightforward.
The first few steps (down to and including the CPYSPLF) can be done by
hand.
Paul E Musselman
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.