Re: SAVSYS running over an hour -- MIDRANGE-L

× 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.

rob@xxxxxxxxx wrote:

Information collected . . . . . . . . : 09/17/09 04:00:01
% of Size in Description Disk 1,000,000 bytes
<<SNIP>>
QSYS 6.56 21409.19 <<SNIP>>
TOTAL 99.77 325505.50

Information collected . . . . . . . : 12/03/09 04:00:03
% of Size in Description Disk 1,000,000 bytes
<<SNIP>>
QSYS 47.08 153583.06 <<SNIP>>
TOTAL 99.82 325677.57
HUGE growth in QSYS!
Running a new RTVDSKINF now so I'll look at that soon.

Note that the largest objects in QSYS, the QADB* database *FILE objects, are not actually saved by SAVSYS; i.e. do not incorrectly infer their size has any impact. Only additional users [and auth entries], configuration objects, OS+options programs, and the temporarily applied\removed PTFs & save files should be there as additional storage being saved. Any other files [e.g. history logs] or receivers [which should not exist in QSYS] might account for such storage. I would suggest using DSPOBJD to review for those objects with created [or restored] date between those two RTVDSKINF dates.

Regards, Chuck

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.