http://try-as400.pocnet.net/index.php?action=history&feed=atom&title=Iconv_conversion_issues_with_CRLF_in_CIconv conversion issues with CRLF in C - Revision history2026-04-06T17:50:22ZRevision history for this page on the wikiMediaWiki 1.43.6http://try-as400.pocnet.net/index.php?title=Iconv_conversion_issues_with_CRLF_in_C&diff=1645&oldid=prevPoC: New2025-12-30T00:03:23Z<p>New</p>
<p><b>New page</b></p><div>Some network protocols such as http want line ends to be terminated with the traditional MS-DOS/Windows '''CRLF''' line wrap. When programming on OS/400 '''in C''', communications to/from the outside world must additionally converted from EBDIC to ASCII and backwards with the standard C library '''<code>iconv()</code>''' function.<br />
<br />
Using the default compiler settings in at least V4R5 converts the CR to ASCII <tt>0x0d</tt> as to be expected, but converts a LF to <tt>0x85</tt><ref>The ASCII Next Line (NEL) control character.</ref> instead of <tt>0x0a</tt>. Network packet dumps hence show the result as <code>0x0d 0x85</code>, which is not the expected sequence.<br />
<br />
Setting the compiler option <code>sysifcopt(*ifsio)</code> fixes this behavior.<br />
<br />
Excerpt from the ''ILE C Programmer’s Guide'', Chapter ''Text Streams and Binary Streams'':<br />
<br />
<blockquote>'''Note:''' The <code>*IFSIO</code> option also changes the value for the <tt>’\n’</tt> escape character value to the <tt>0x25</tt> line feed character. If <code>*NOIFSIO</code> is specified, the <tt>’\n’</tt> escape character has a value of <tt>0x15</tt>.<br />
</blockquote><br />
<br />
== Weblinks ==<br />
* [https://comp.sys.ibm.as400.misc.narkive.com/giSN736Z/iconv-fails iconv() fails?], Narkive Newsgroup Archive<br />
<br />
== Footnotes ==<br />
<references/><br />
<br />
[[Category: Programming]]</div>PoC