Re: MCH3601 error (Jeffrey Young)

Thanks.  This brings up another question I had about Large File Support.
Does the O_LARGEFILE value act the same as SYSIFCOPT(*IFS64IO) in a C
create command?  

If so, is the return from the read/write not a 20U 0, not a 10I 0?
(Along with the nbyte field -- unsigned long long instead of a signed
long (int)?)  From another project enabling our C programs for large
files, I know that off_t and size_t get redefined as unsigned long longs
when using *IFS64IO. 

Do the unix style calls have 64 bit versions, as fopen() =>> fopen64()?

> ------------------------------
> 
> message: 4
> date: Wed, 6 Jul 2005 08:26:33 -0700 (PDT)
> from: Jeffrey Young <cooljeff913@xxxxxxxxx>
> subject: Re: MCH3601 error
> 
> Try using the UNIX style API's ... open, close .. etc.
> 
>> SOME REMOVED <<

>      D*                                            Large file access
>      D*                                            (for >2GB files)
>      D O_LARGEFILE     C                   536870912
> 

>> MORE REMOVED <<