Don't know how often you IPL, but I had a customer who once was in a similar
situation, and what I did was write a routine, that deleted any objects in
QRECOVERY that were older than 5 or 7 days (can't remember which). We got
the wild growth down, and this worked fine for them. At each IPL it deletes
pretty much everything but the *JRN.
I wouldn't delete everything in QRECOVERY every day, as you may have
programs that have been recompiled that the old version could still be in
someone's invocation stack, and deleting that object while it's in their
stack will cause a problem when they return back to the program on the
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jones, John (US)
Sent: Thursday, March 20, 2008 9:10 AM
To: Midrange Systems Technical Discussion
Subject: RE: QRECOVERY library and its purpose on i5/OS
The QRECOVERY in one of our LPARs has over 33,000 objects in it, taking
over 300GB DASD. This message drove me to start an inquiry as to what
can be done about it.
Considering what the 70GB disks costs when the hardware was purchased,
it's probably taking around $10K in resources (over 5 disks + a portion
of the RAID card & the 0595).
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