|
Right, but the question was concerning the read() function not open64(). My point was that read() (the same read() function) works with both forms of the open() and open64() functions. -Bob Cozzi www.RPGxTools.com If everything is under control, you are going too slow. - Mario Andretti -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Wolcott Sent: Wednesday, July 06, 2005 9:09 PM To: rpg400-l@xxxxxxxxxxxx Subject: open() vs open64() (Was: Re: MCH3601 error (Bob Cozzi)) The 64 bit versions are specifically for reading files over 4GB. Using the standard 32 bit C APIs, you can not open a 4GB+ file. In 'C' you need to specify 'SYSIFCOPT(*IFS64IO)' on the create command to get the 64 bit APIs. (*IFSIO gets you the 'standard' 32 bit APIs.) > The APIs are prototype don the rpgiv.com website. > http://www.rpgiv.com/downloads/ > > The directly link to the page you want is: > http://www.rpgiv.com/cgi-rpg/viewsrc?FILE=QCPYSRC&LIB=RPGLAB&MBR=IFSPROT OS > > Read and Write use either "handle" to read the data. You have, what about > a > 2GB "limit" on the data you read at once, but that doesn't mean you can't > read multiple times to get all the data. > Scott K. would know this stuff best, but I don't think it matters which > open() or open64() you use when reading the file. I always use open64() > since it is actually 'faster' according to IBMers.
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.