1 - We don't save spool files. I've tried to repeatedly drill into users
(back when it wasn't easily supported by the OS) that they shouldn't rely
upon spool files being there. The data should be relied upon. Granted, I
understand that some spool files are transitional and hard to duplicate.
Even though it's now easier we still do not save spool files.
2 - We use the system value QLOGOUTPUT and changed joblogs to NOT spool up
but instead go into 'pending' state instead. If you just 'have' to have a
spool output (to send to IBM or whatever) you do a DSPJOBLOG JOB(...)
3 - We use the GO CLEANUP menu to automatically delete these with
1. Change cleanup options
Number of days to keep: Job logs and other system output . . . . . . . 7
4 - We delete all spool files after 90 days. No exceptions. Remember,
with that QLOGOUTPUT set joblogs are not spool files unless someone does
Maintaining job logs for a long period of time:
- wastes disk space
- increases the number of jobs in your system, which can have it's own set
of ill effects
- increases your backup time (and often your system outage) if you save
spool files, and you have joblogs spool up.
- encourages sloth in dealing with problem issues.
Our busiest 'traditional' lpar has only 7 spool files in QEZJOBLOG. Only
one was a 'traditional' application. The rest were qejbsvr type jobs.
Weird that something of IBM's would default to spooling output. Even if
you don't change your system value IBM has changed many of their job
descriptions to LOGOUTPUT(*PND).