Re:
> MPEiX LISTF command:
> FILE:  DONORS.DATABASE.DEV             
> EXT SIZE:  26(SECT)                         WRITE   : ANY        
...  
> MPEX LISTF command:
> EXT SIZE:  26(SECT)                         WRITE:   ANY

> My app (getting the extents info using the FFILEINFO intrinsic) gives  me:
> EXT SIZE:  128                              WRITE   :  ANY                    

The first question in cases like this is: *is* your
application getting 128, or is it just *printing* 128
for some other reason?

To answer that, DEBUG is your friend.  Simply set a breakpoint
at FFILEINFO, find the call that's trying to get the
extent size, note the overall status parameter's address
and the status array parameter address, and the address
of the area that will be given the result.  Set a breakpoint
at the exit of FFILEINFO, and continue.  When you hit
the exit's breakpoint, examine all of the above to
determine if any errors occurred, and to see what value
was returned.  If no erros, and 128, then we move on to
the next question.

The second question is: what the hell *is* "extent size"
on MPE/iX for any file with more than one extent? :)

On MPE/V, extent size was meaningful ... every extent of
a file (except the last extent) was of a fixed size (for
that file).  (The last extent was the same size or smaller.)

On MPE/iX, any given extent has no enforced relationship
to the size of any other given extent in a file!
(Read the note about extentsize (other than the missing
note for item 69 :) in the FFILEINFO documentation.)

So, if there's no programming error, I'd say "I have no
idea why you're seeing different values ... but it's
not really important.  If it's an MPE bug, it's not
going to get fixed, *and* your program has no business
trying to report "extent size" :)

Stan
-- 
Stan Sieler
[log in to unmask]
www.allegro.com/sieler/wanted/index.html 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *