Ah yes, I mis-typed/fat fingered the reply. As you say, it SHOULD read EDCICONV.
And, yes Unicode allows for over a million possible character combination. National Language support in the mainframe allows for the characters in basic mapping plane 0, so only about 65,000 character combinations. And IBM-037 only has 256 combinations. So, be aware of character loss as you transform from one to the other. On Sat, Feb 8, 2020 at 11:45 AM Paul Gilmartin < [email protected]> wrote: > On Sat, 8 Feb 2020 09:09:58 -0600, Paul Gilmartin wrote: > > >On Sat, 8 Feb 2020 09:37:29 -0500, Cameron Conacher wrote: > > > >>I use ICONV. > >> > >>//MYSTEP EXEC PROC=EDICONV, > >>// INFILE='MY.input.file.name(member)', > >>// OUTFILE='My.Output.FileName', > >>// FROMC='1208', > >>// TOC='IBM-037' > >> > >> > >>The PROC is licensed IBM material. It executes program EDICCONV > >> > >Is the documentation available only with purchase? > > > Ah! Do you mean perhaps, JCL procedure EDCICONV? > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.cbcux01/iconvubatch.htm > > I wonder what was the motivation to require preallocated data set > names rather than the more flexible alternative of DDNAMEs? > > >How does it handle characters absent from IBM-037? > > > >1208 is UTF-8, not UTF-16. I assume the example is schematic. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
