…the size of a DB2 data base…
Please clarify what you mean by “data base”.
Do you want to know the space taken by records in your physical files? Do you want to include deleted records? Do you want to include the sizes of the objects that hold the records? Are indexes and views included? Do you want to include allocated space that isn’t used yet?
Do you need to know for individual libraries (schemas)? Or do you want all libraries at once? Should system or product libraries be included?
Should the size include directories outside of libraries? (DB2 generally doesn’t care about directories and streamfiles outside of libraries — unless your DB2 tables use DataLinks or similar features.)
It might be easiest if you describe the business problem that you need to solve.
Using opsnav and selecting databases then schemas the size difference from a dsplib *print was equal to programs and source files that had been placed in the lib.
So with opsnav you get database objects only and probably more accurate. The grouping was different also by table, index, sqlpkg etc instead of straight alpha sort.
…the size difference from a dsplib *print was…
For me for the first library I tried (my *CURLIB), there was no size difference nor object count difference. Everything was included in the size both ways.
But there may be differences in iNav versions and in how the size and object count was requested. This iNav is V5R3, though I also tried 6.1 with the same result. I requested size and count info by viewing the Storage tab of the Properties page of the schema. The only other way that seems available is to view the description of each object and manually total things up. Can you give a little more detail?
Hi Tom, If you set IFS folder properties under the security tab(at least I think this is the property that turns this on) to “allow object scan” the system will do a real time scan and give you folder size and file count.
Oh, never mind I didn’t read your post carefully, you already have scan on.