Usage notes for the TRANSLATE option for the FTP client

To use the TRANSLATE option to load and use a customized DBCS translation table for the FTP client, an SBCS table data set must also exist for the data_set_name chosen with the TRANSLATE option.
If the SBCS table data set does not exist, the FTP request fails even if a valid DBCS table data set using that name exists.
ATTENTION: Do not use the TRANSLATE option for the FTP client if the SBCS table you need for data transfer does not support standard encodings for the portable character set. Such a translation table can adversely affect the EBCDIC to ASCII conversion of commands sent over the control connection.
For information about using FTP.DATA to specify different SBCS tables for control and data connections, see z/OS Communications Server: IP User's Guide and Commands.

If you require a local DBCS translation table, you must name it in correlation with the standard client search order. For example, if you had a custom Kanji table you could name it user_id.FTP.TCPKJBIN.