Re: Size of QRPLOBJ is large when empty

AFaIK there is still no "method" provided to truncate the index object which implements the *LIB object; the "context" object. That is, the CLRLIB probably does little more than perform the ordered DLTxxx requests against each "xxx" object type, and I expect there still is no additional "truncate index" operation performed after the delete of the objects. Thus I expect the index object still will only ever grow, never shrink, without DLTLIB to effect the destroy of that index.

I do not have the ability to test, but both the SIZE in the DMPOBJ of the *LIB and the object size shown in DSPOBJD OBJTYPE(*LIB) I expect would not reduce [much, if any] for a CLRLIB request performed against a library which has or had a very large number of objects; while I posit the index will not shrink, other composite pieces of the *LIB might still decrease in size somewhat. A request to RCLLIB however, may reduce the SIZE of the *OIRS and *QDIDX objects comparing a DMPOBJ from before the request and after.

FWiW I do recall there had been a KB article published long ago about the library size, for how the index size will never decrease; I could not find that, else I would have included a link.

Regards, Chuck

On 1/29/11 11:41 AM, Pete Massiello wrote:

What about CLRLIB? How would that affect it?

CRPence on Saturday, January 29, 2011 1:35 PM wrote:

On 1/28/11 9:28 AM, Luis Rodriguez wrote:

Just curious...
Is that index saved with SAVLIB? What happens if the OP does a
SAVLIB/RSTLIB to QRPLOBJ?

The RSTLIB to a new library name causes an effective CRTLIB, thus
a new library "index" implementation object; growing only with each
object restored also as part of the RSTLIB request. <<SNIP>>

And while the SAVLIB\DLTLIB\RSTLIB combination could reduce the
index size for another [e.g. a user] library, except for a [near]
empty library, I would probably almost never do that <<SNIP>>