Re: lstat64 returning wrong size

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
It was a coworker who was having problems with lstat64.  He got it
working, something about a datastructure was defined wrong in the sample
he got from this site.  Once he fixed that it seems to be working.  I just
noticed a reply from him to the RPG list.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




Vernon Hamberg <vhamberg@attbi.com>
Sent by: midrange-l-admin@midrange.com
07/10/2002 06:07 PM
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Fax to:
        Subject:        Re: lstat64 returning wrong size


Try the Qp0lGetAttribute API - request the 64-byte size items.

Also, did you activate the large size defines?

At 11:47 AM 7/10/02 -0500, you wrote:
>On extremely large objects (over 2,685,551,104) lstat64 will return the
>size of 2,685,551,104.  For example I have an item in our ifs which has a
>size of 67,110,060,544 as shown by WRKLNK.  But lstat64 returns it's size
>as 2,685,551,104.  We have reported that Op's Nav has a bug in which it
>shows the wrong size also.  We've not yet reported the lstat64 issue.
>(Wanna bet they're related?)
>Any suggestions for a workaround?
>
>Rob Berendt

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.