Re: wrksyssts non DB-fault paging

Are you serious, Steve? "Keep up with" in the sense of *actively* keep up
with, i.e. keep checking on, i.e. using CPU cycles?

This could be a problem for me, too. We have tons of spool files sitting
around, mainly because it is hard to automate cleanup of our individual
users' stuff because they have legitimate reasons to keep some things for
long periods of time. Certainly though, the vast majority of it is clutter,
because of not enforcing an automated cleanup.

I just thoght it was wasting some disk space. If the system is actually
doing work to maintain this clutter, I need to invest a little more time
into a cleanup strategy.

What kind of system resources are consumed by these old jobs' spool files
laying around?

THANKS,
-Marty

----------------------------------------------------------------------

date: Mon, 29 Mar 2004 11:47:59 -0600
from: "Steve Landess" <sjl_123@xxxxxxxxxxx>
subject: Re: wrksyssts non DB-fault paging

...
1) Why do you have over 45,000 jobs in the system?
You're probably keeping too many spooled files around...
Remember, the system has to keep up with these jobs even after they have
ended.
...