Tony, Our Co:Z Toolkit (SFTP, Dataset Pipes) can use either Unicode services or iconv(), although it defaults to using iconv(). We allow users to optionally specify the "technique" search string (we default to LMREC). When we use iconv, we are going to use this to set _ICONV_TECHNIQUE.
Regarding the line end fiasco - our code handles line terminator separately, and we fix them up to avoid the dreaded ASCII NEL, which only an IBM architect would want :-) The point of adding this particular table (the old STANDARD.TCPXLBIN) to Unicode Services is that there are rare customers who are dependent on the exact handling of "control character" conversions in that table, which the Unicode Services tables don't seem to provide a direct replacement for. Kirk Wolf Dovetailed Technologies http://dovetail.com On Wed, Feb 1, 2012 at 6:53 PM, Tony Harminc <t...@harminc.net> wrote: > <snip> > How are you expecting a user conversion technique to fit into your or > a customer's environment? In other words, how will the fact that you > want a different conversion for these codepage pairs to be used be > communicated to the program? Will it explicitly request a technique 2 > conversion, or is it expected that things will fall through to > technique 2 because of the system configuration? Are you using iconv() > or calling the Unicode services directly? > > > 4) verify with iconv that it works. We have a simple utility in Co:Z > that will display single byte translate tables: > > > >> *showtrtab -s IBM-850 -t IBM-037 -q 2* > > What does that call internally? > > Tony H. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
