Re: Line-ending for IFS test stream file

[Jon Paris <jon.paris@xxxxxxxxxxxxxx>]

I thought that if you were using  o_TextData you had to code “your” CRLF as being the appropriate hex values that will result in CRLF post conversion.  What values are you using and what is the target code page?


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jun 2, 2015, at 10:11 PM, MichaelQuigley@xxxxxxxxxx wrote:

> Hi folks,
>
> I've got a program which opens, reads, scans the data modifying some of 
> the content, then writes and truncates a file in the IFS. It uses the 
> open, write, ftruncate, and close APIs. The open uses the o_TextData flag 
> so the CCSIDs are automatically converted for my program to manipulate the 
> data on the IBM i. Everything works great with the exception that the line 
> ending carriage-return and line feed (CRLF) is being changed. When I debug 
> the program and step through file scanning, the CRLF is being processed 
> correctly--i.e., I see the two bytes processed at the end of each line. 
> But when the file is re-written and closed, the CRLF is modified to simply 
> be a carriage-return.
>
> This isn't a problem most of the time, but there are cases where the PC 
> program which later uses the processed data isn't recognizing the last 
> line of data since it doesn't end with CRLF. Is there an option I've 
> overlooked or something I can do to preserve the CRLF?
>
> Thanks,
> Michael Quigley
> Computer Services
> The Way International
> www.TheWay.org
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.