|
Based on a test, ALCHSS allocates 16 bytes + your allocation size. So 16 user bytes is 32 actual, 32 user bytes is 48 actual. Not sure if the 16 bytes of the system is before or after the allocation. Also not sure what it is used for. Steve Richter -----Original Message----- From: mi400-admin@midrange.com [mailto:mi400-admin@midrange.com]On Behalf Of Leif Svalgaard Sent: Monday, April 08, 2002 6:58 PM To: mi400@midrange.com Subject: Re: [MI400] Space pointers From: John Taylor <jtaylor@rpg2java.com> > > I would be careful when looking at the allocated size using MI. I'm not > > sure if MI will report the actual number of bytes used, or the allocated > > memory. I'm not real familiar with what goes on behind the scenes in the > > AS/400. > > Yes, that's a good point. The MI template isn't clear regarding whether the > allocation size reported is referring to the minimum allocation requested, > or the actual storage units used. (I'm guessing that by "bytes used", you > weren't referring to the length of data.) > > Steve, Leif, can either of you shed some light on this? > when you create an allocation the minimum size is 512 bytes (one standard storage block). I would assume that the size at all time would be a multiple of 512 bytes. The page size of a RISC AS/400 is 4096 bytes, but since MI is the same for both CISC and RISC boxes, I think that 512 bytes is the real allocation unit. _______________________________________________ This is the MI Programming on the AS400 / iSeries (MI400) mailing list To post a message email: MI400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mi400 or email: MI400-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/mi400.
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.