On Sat, 3 Jan 2026 12:40:56 -0600, Kirk Wolf wrote: >Peter, > >I would assume that IBM didn't implement UTF-8 -> EBCDIC "MOVE" conversions >because of the issues: > >- What if the source field ended in the middle of a UTF sequence? Error or >Subsitute char? >- What if there is no EBCDIC character defined? Error or Substitute char? > <https://urldefense.com/v3/__https://www.ibm.com/docs/en/cobol-zos/6.5.0?topic=cobol-converting-from-utf-8-unicode-representation__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!OZIq1MM33NpZ6H5CIG_Zkkwxg1u296SY8WhWJy_oj0ZPQ-C4R1Fs5CTo23TQD0hsP9MiPjT_FYjeIx-_fXgOit60sB22hsIbUDdS-8-1$<https://urldefense.com/v3/__https:/www.ibm.com/docs/en/cobol-zos/6.5.0?topic=cobol-converting-from-utf-8-unicode-representation__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!OZIq1MM33NpZ6H5CIG_Zkkwxg1u296SY8WhWJy_oj0ZPQ-C4R1Fs5CTo23TQD0hsP9MiPjT_FYjeIx-_fXgOit60sB22hsIbUDdS-8-1$>>
>Were you able to get CUNLCNV working from COBOL? You could roll your own with >that and control how you wanted it to behave. Besides, by the time IBM adds >it to COBOL you won't need it any more :-) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
