Re: Problem writing to a IFS file -- RPG400-L

Hi Griz,

[SNIP]

StringVal = 'LINE 1                   ';
StringValW = %TrimR(StringVal) + CRLF;
Fd=write(RC2:%addr(stringvalW):%Len(%Trim(stringvalW)));

[SNIP]

The output in the IFS file reads as follows:
LINE1 LINE2

Is StringValW 2 characters longer than StringVal? If not, you could runout of space for the CRLF in the StringValW field, which would cause theproblem you're experiencing. In other words, if StringVal is 100A,StringValW needs to be 102A.

Would I be better off using O_TEXTDATA in place of O_CODEPAGE if I wasdealing with a text file/HTML file?


O_CODEPAGE and O_TEXTDATA aren't alternatives to one another.

O_CODEPAGE tells the operating system the codepage of the data you intendto write to the IFS. In this case, you've told it that the code page is819 (which is ISO 8859-1 ASCII)... which means that if you're doing itright (and I don't think you are) the data from your program would have tobe in that codepage.

O_TEXTDATA means that you want the operating system to translate from yourjob's codepage to the file's codepage when you write, or from the file'scodepage to the job's codepage when you read. O_TEXTDATA is onlymeaningful if it's used on a file that already exists, or if you alsospecify O_TEXT_CREAT. If you're creating the file on the same open()statement, and haven't specified O_TEXT_CREAT, then it won't have anyeffect.

Usually on pre-V5R2 systems, you'll open the file once to create it andassign a codepage. Then close it. Then open it again, this time withO_TEXTDATA so that the system will automatically translate it.

however, the codepage/textdata issue has nothing whatsoever to do withyour text appearing on the same line as the previous text. Lines of textend when the line delimiter (in this case, CRLF) is found. The only reasonit would fail to advance to the next line is if the delimiter isn't foundfor some reason. Somehow you're failing to get that CRLF into the data.