Hi Jeff,

Yes, the IFS e-book on my web site was written for v4r5... The O_TEXT_DATA feature (and it's corresponding 5th parameter) was added to the OS in V5R2. You can get the current copy of IFSIO_H here:

http://scottklement.com/rpg/copybooks/ifsio_h.rpgle.txt

It's still unclear to me what the actual cause of the problem is... Here's how I'd call the open() API... maybe that'll help.

IFS_File_Name = '/excel/xml/I12456_0.csv';

FileDs = open( %trimr(IFS_File_Name)
: O_CREAT + O_WRONLY + O_TEXTDATA + O_CCSID
+ O_TEXT_CREAT + O_INHERITMODE
: 0
: 1208
: 0 );

The fact that the file shows up on IBM i, but not on Windows is not a commonplace error. It implies (as I said before) that there are two copies of the file.

Two possibilities:

1) That there are two locations, and you're viewing different locations from each source.

2) That you didn't trim the trailing blanks from the filename, and so you have two copies, one with blanks in the filename, and one without.


On 6/18/2012 2:07 PM, Jeff Young wrote:
Scott,
1. The proper number of bytes for the file is 100. This shows in the
WRKLNK option 8 on the i. The file consists of 2 records each 50 bytes.

2. In Windows (XP Pro) when I view the list of files on the mapped drive,
it shows 1K.
When I double click on the file name, nothing happens. The file does
not open and no error is issued.

3. When viewing the properties in Windows, the file shows as 0 bytes.


I am using the IFSIO_H copy book from your book, although it may be an
older copy as I had to modify the Open prototype to add the fifth parm
required for O_TEXT_CREAT.

The code I use for the Open of the file is shown in my original post.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.