At 03:21 PM 12/24/2023, Paul Gilmartin wrote:
On Sun, 24 Dec 2023 14:18:34 -0600, Michael Oujesky wrote:
>Just as an aside, the default EBCDIC to ASCIIi translation table in
>FTP has issues with some special characters. We used CONVXLAT
>against TCPIP.SEZATCPX(EUS) to create one that works for the texts we
>have, Then in the FTP control statements, used LOCSITE SBDataconn=
>to specify use of the created translation table for the transfer.
>
Nope, kept it in it's own dataset.
Did you need to create your own table? Did you need to add it to LNKLST?
Nope, just used EUS from the standard TCPIP library without any
tweaks. Just pointed to it's own sequential file, but would probably
install it via a USERMOD if were going to make it the default text
translation table.
Do you have unusual code pages?
Nope, just using the original system default.
More easily, I have used SBDATACONN(IBM-1047,ISO8859-1)
<https://www.ibm.com/docs/en/zos/3.1.0?topic=protocol-sbdataconn-ftp-client-server-statement>
More absurdly, in
<https://www.ibm.com/docs/en/zos/2.1.0?topic=only-customizing-translation-table>
When accessing z/OS UNIX files, you must specify the OEMVS311
translation table ...
"must"? IOW, IBM's default doesn't work.
--
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
