I’m not aware of anything that controls the aggregate sizes of all of the objects in a library.
Sizes are controlled in multiple ways.
For example, you might create a profile that is the owner of the objects in a library. You can control the maximum space used by a user profile with the MAXSTG() attribute of the profile.
Or you might assign thresholds to your ASPs. The system will send messages when objects use space in that ASP that causes the size threshold to be crossed.
But I don’t think you can automatically limit a ‘library size’. At least, I don’t recall ever seeing anything like that. You can, of course, write a program that retrieves the size of all objects in a library. Your program would do whatever you chose when the sum of the sizes was too high.
The size of the Library is the size of all the links within that library. Not the size of all the data within the Library. Do the math. When you do a WRKOBJ on the library vs. a WRKOBJ on the objects within the library.
ASP are disk related. They are not library related. Unless you stipulate that every time a library is created.
The size of the Library is the size of all the links within that library. Not the size of all the data within the Library.
True. However, the system does make the aggregate size available to you. The Retrieve Library Description (QLIRLIBD) API can return attribute key 6, “Library size information”, which is described as “Library size information. Information about the size of the library, which includes the size of the objects in the library plus the size of the library object itself.”
When a value is directly available through an API call, it’s plausible to expect that the system might be able to react to it.
But I don’t think this is one that works.