Re: Code Page Problem with Scott's IFS Book

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Mike wrote:
> Okay... I found an example browsing through the archives and it works. For
> the sake of documentation, this works:
>
>          callp unlink ('/web/customerService/webCategories.xml');
>          fd = open('/web/customerService/webCategories.xml' + x'00':
>                    O_CREAT+O_WRONLY+O_TRUNC+O_TEXTDATA+O_TEXT_CREAT+O_CCSID:
>                    RW*OWNER + RW*GROUP + R: 1208);

You don't need to add x'00' to the path name (unless your prototype is 
wrong).  That's what options(*string) does, it adds the x'00' for you.


Note that the code you posted requires V5R2.  (That's when the 
O_TEXT_CREAT flag was added to the IFS APIs).  Prior to V5R2, you need 
to open the file twice, once to assign the CCSID/Codepage, and a second 
time to do translation.

Translation only occurs if the file already exists, thats why you open 
it twice, once to create the file, and a second time to do translation. 
 (And that's what the O_TEXT_CREAT flag solves -- it allows translation 
on a file that doesn't exist... or, in IBM's wording, allows TEXT mode 
when CREATing a file.)

The O_CCSID keyword requires V5R1.  Prior to that, full CCSIDs were not 
supported in the IFS, only code pages.

My e-book was written for V4R5.  So it uses code pages, and it opens the 
file twice.  See sections 5.5 and 5.6 where it demonstrates this process.

However, if you don't expect your program to run on a pre-V5R2 system 
(which is probably a reasonable assumption today) then use O_TEXT_CREAT 
and O_CCSID...