× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Dean,

I would think it would work for QPJOBLOG.

Try this:

CHGPRTF FILE(QPJOBLOG) EXPDATE(*DAYS) DAYS(14)

which will keep _every_ QPJOBLOG on the system for 14 days. Since you're
changing an IBM supplied object, remember that a release update or possibly
a PTF could change it back to EXPDATE(*NONE). To remedy that, have a job
scheduler job run every night that sets the print file QPJOBLOG to whatever
you want.



On Wed, Feb 27, 2013 at 3:14 PM, Dean Eshleman
<Dean.Eshleman@xxxxxxxxxxxx>wrote:

Jeff,

Reviving an old thread here.

Does this method work for job logs? I would like to keep the last couple
of job logs for each production job around. Right now, we keep job logs
for 2 weeks and then they are purged. This doesn't work very well for jobs
that run less frequently than every week.

I tried doing a OVRPRTF EXPDATE(*DAYS) DAYS(10) on QPJOBLOG within the
job, but that didn't work. I tried with the Override scope set to *JOB and
*ACTGRPDFN. The expiration date on the job log was blank in both cases.
Any ideas on how to get this to work for job logs?

Dean Eshleman
Software Development Architect

Everence Financial
1110 North Main Street
PO Box 483
Goshen, IN 46527
Phone: (574) 533-9515 x3528
www.everence.com<http://www.everence.com>

On 9/5/2012 1:15 PM, Jeff Crosby wrote:
As an alternative, how about expiring spool files?

I don't know exactly what you may be after, but you can do either OVRPRTF
EXPDATE(thedate) or OVRPRTF EXPDATE(*DAYS) DAYS(1). Then use a job
scheduler job to run once a day and run the DLTEXPSPLF command. It gets
rid of all expired spool files.

I use the DAYS() example a lot. Some reports 1 day, some 3 days, some 30
days, etc. There are different logs or registers that I create, never
intending to print, but may want to look at if an issue arises.





________________________________________
Confidentiality Notice: This information is intended only for the
individual or entity named. If you are not the intended recipient, do not
use or disclose this information. If you received this e-mail in error,
please delete or otherwise destroy it and contact us at (800) 348-7468 so
we can take steps to avoid such transmission errors in the future. Thank
you.
_______________

______________________________________________________________________
Confidentiality Notice: This information is intended only for the
individual or entity named. If you are not the intended recipient, do not
use or disclose this information. If you received this e-mail in error,
please delete or otherwise destroy it and contact us at (800) 348-7468 so
we can take steps to avoid such transmission errors in the future. Thank
you.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.