*The* code pages used for *that* default (?) translation would utterly depend on the FTP server, the FTP client, and their configurations. For example, my WS_FTP is configurable such that .txt files get translated (and the .txt is truncated or appended for PDS member names) but others do not. Yes, all that is documented.
I think the supported way to create custom translation tables is through z/OS Unicode Services. My (so-to-speak) former product made extensive, configurable use of Unicode Services various EBCDICs to ASCII or UTF-8 and I was very impressed with its ease-of-use and performance. I'm a fan! And if you really want absolute peak performance for simple 1:1 (non-UTF-8, in other words) translations it is easy to give it a table of x'00', X'01, x'02', ..., translate it from/to your desired character sets, and then use it with the TR hardware instruction. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, July 9, 2020 9:12 AM To: [email protected] Subject: Re: SuperWylbur Users On Wed, 8 Jul 2020 21:51:11 -0700, Charles Mills wrote: >> Why is a utility targeted for IBM mainframes (other than Linux for z) >> translated into "ASCII"? > >My guess is there was no "why." They just downloaded it and the default was >ASCII translation. It's bitten me more times than I care to admit. > Are the code pages used for that default translation documented? I know, rather, there is documentation for using Assembler and Binder to create private translation tables painstakingly by typing hex constants, but no supported simple way to create such tables in terms of given CCSIDs. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
