|
Dave: The outfile from DSPOBJD does have a field ODOBSZ, which used to be always the object size, but it is defined as a 10.0 field, so it does not correctly report objects that are 10 gigabytes or more. To calculate object size, multiply field ODBPUN (bytes per unit) times field ODSIZU (size of unit). As long as all your objects are 9,999,999,999 or less, you're okay. However, as soon as you get an object that is 10 gig, the ODOBSZ will produce the 9,999,999,999, and you're be in error by the difference. BTW, if you use QRYDOCLIB to determine size of documents in Shared Folders, it has the same problem but goes only 8.0 (I think). The solution there is to use DISKTASKS, or if continuing to use QRYDOCLIB, retrieve the object size from the object description if you find any documents with size 99,999,999 in the QRYDOCLIB outfile. Regards, Debbie Gallagher ******************** Original Message ******************** Are there any circumstances when the product of ODBPUN and ODSIZU is not the same as ODOBSZ? This is the field I've always relied on for object size. Dave Kahn +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.