|
I guess, if we're talking about disk space efficiency, we should be taking into account how much disk is reserved for the file, rather than how many bytes of data there is. Therefore, I would suggest using the 'Allocated size of object' from the WRKLNK/8 display rather than the 'Size of object data in bytes'. But, aside from that, I think you're testing it just as I would. And, as I suspected, the IFS is much more efficient on disk space, because it doesnt have to pad each record out with wasted spaces. And, the efficiency of the IFS is not something new. It was also more efficient (I just tested it) way back in V3R2... So I'm not sure what Mr. Barsa is referring to, unless he's worried about speed (but I thought he said disk space!) On Tue, 15 Oct 2002 rob@dekko.com wrote: > > About the only concern with this test, is I should probably check for a > list of members. The overhead of the object itself, without any members: > > RMVM FILE(ROB/SCOTT) MBR(*ALL) > DSPOBJD OBJ(ROB/SCOTT) OBJTYPE(*FILE) > Object Type Attribute Size > SCOTT *FILE PF 8192 > > ADDPFM FILE(ROB/SCOTT) MBR(ORD500) > DSPOBJD OBJ(ROB/SCOTT) OBJTYPE(*FILE) > Object Type Attribute Size > SCOTT *FILE PF 24,576 > > Oh well, plugs that gap. The overhead is definitely in the member data. > Not in the file. Not in the member header. But the member data. > > Rob Berendt > > Good question. Is the following a valid test? > > CRTSRCPF FILE(ROB/SCOTT) > CPYF FROMFILE(BPCS405CDS/QRPGSRC) TOFILE(ROB/SCOTT) FROMMBR(ORD500) > TOMBR(*FROMMBR) MBROPT(*ADD) > > DSPOBJD OBJ(ROB/SCOTT) OBJTYPE(*FILE) > Object Type Attribute Size > SCOTT *FILE PF 2,220,032 > > CPYTOSTMF FROMMBR('/qsys.lib/rob.lib/scott.file/ord500.mbr') > TOSTMF('/rob/scott.rpg') > > WRKLNK OBJ('/rob/scott.rpg') > 8=Display attributes > Size of object data in bytes . . . . . : 993,443 >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.