Re: SAVSYS running over an hour

[CRPence <CRPbottle@xxxxxxxxx>]

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