On Fri, 10 Mar 2006, Mark Koehn wrote:

>I'm attempting a port of curl/libcurl to z/OS 1.7 ussing the USS subsystem.
>I was wondering if someone familiar with workings of libcurl could point me
>to the locations where they would add EBCDIC to ASCII and ASCII to EBCDIC
>translations from the network and to the network.

As luck would have it, I've been working on a port of libcurl to IBM's TPF
platform, which is also EBCDIC.
My work has been for the FTP client only, but it lays a lot of the
groundwork for the other clients.
I plan to submit my changes for review later this week.
At present they will allow libcurl to do ASCII/EBCDIC conversions using
either iconv or a user-specified translation callback, so they should be
generic enough to work with any EBCDIC platform.

>I'm expecting that sending data of the network will be in ASCII and
>translations would need to be done upon receiving info from the network and
>prior to placing data on the network.

Yes, everything going over the network must be translated to/from ASCII,
with the exception of binary data (bin mode) transfers for FTP.
There might be more exceptions for the other protocols but I haven't
researched it.

-David McCreedy
Received on 2006-03-13