Re: Creating and writing to IFS in multiple releases

["Chris Wolcott" <CWolcott@xxxxxxxxxxxxxxxxxxxxxx>]

Thanks.  I lucked out in reading an IFS file because the codepage
defaults to 37 and the data is translated automatically from 1252, but
writing one that I could access via DOS programs was driving me crazy.
What I had read said the conversion happens auto-magically, but the idea
that the file had to exist with the ASCII codepage tagged escaped me.
The /COPY member I'm using is prototyping _C_IFS_fopen(), not open() as
you do, but by using the option 'w codepage=1252' on my first fopen(),
closing it, and then using 'a codepage=37' on my second open the data I
write comes out OK instead of giberish.  This will make life easier than
having to write out an RPG file and using CPYTOSTMF to get it to the
IFS. 

--- Original Message --- 

*** Much usefull info snipped ***

> I'm unclear on what you mean by "nobody seems to agree on the
prototype."
> There are many ways to prototype the same function -- just make sure
you pick a sample program that actually WORKS instead > of one where the
author posted his code to get help because he was stuck.

Iconv() returns a structure, and some posts said you must have a
corresponding DS and others said just an INT.  I guess both work as the
return value is the first value in the structure and is an int.  Most of
the posts I found on iconv() were debating this point rather than
telling how to actually use the function.