I assume that's because the library itself is an object, probably a list of the objects subsumed by it. Then this raises the issue—do we get the size of the library object, or the size of the library's contents? E.g., were we to DSPLIB and total the sizes, we don't include the size of the *LIB object itself.
DSPLIB doesn't show the size of the library object. The size of the library object is only accounted for by looking for it in QSYS. I assume that the library object lives in the ASP where the library exists (new ASPs only). If you're worried about the size of the library object, you are getting very detail oriented.
To strike a balance here, library objects can grow huge, particularly if they have contained lots of objects at one time in their life.
If you have a library object that's gotten out of hand and want to (effectively) resize it:
- create a new library object with a temporary name
(be sure to replicate ownership, ASP and specific authorities)
- move all the objects from the old library to the new one with the temporary name
- after checking that the old library is empty, delete it
- rename the new library to the same name as the old library.
And they say that turkey is supposed to make me sleepy.
Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.
400 > 390
Private mail should be sent to firstname.lastname@example.org +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: email@example.com +---