I would appreciate that also. I would like to see the specific reason code.
My reading is that the error occurs on a call to CUNLINFO, which is optional in that it did not exist before V1R10 and you can use Unicode services very effectively without CUNLINFO. That may be why iconv succeeds, at least in some circumstances. CUNLINFO does not do translation, it tells you about your intended translation. You can call CUNLINFO (writing from memory here) and determine that translation from CCSID nnnnn to CCSID mmmmm is or is not supported, that CCSID nnnnn is single-byte EBCDIC or is MBCS ASCII, and so forth. Peripheral to actual translation. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Leonardo Vaz Sent: Thursday, October 01, 2015 10:48 AM To: [email protected] Subject: Re: Unicode services Red alert I am trying the following command after IPLing with a 2016 date and it works fine: iconv -f UTF-8 -t IBM-1047 < my_ascii_file Could anyone reproduce the error described in the red alert? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
