Single-byte character (SBCS) support

Data conversion occurs for single-byte data on the data connection when ENCODING=SBCS is in effect and the data type is ASCII. For more information, see the FTP.DATA statement ENCODING in the z/OS Communications Server: IP Configuration Reference and the SITE ENCODING command in the z/OS Communications Server: IP User's Guide and Commands.

If you choose SBDATACONN as a statement in the FTP.DATA file or with the SITE SBDATACONN command, the FTP server builds a translation table using the code pages specified by SBDATACONN. If you receive the following reply to the SITE command, ask for a trace of the server with the UTL option to determine which characters cannot be translated.
200
Some characters cannot be translated between codepage_1 and codepage_2 .
If none of the untranslatable characters appear in the data, the data transfers are not affected. If, however, one of the untranslatable characters does appear, the data transfer fails and the client receives the following reply:
557
Data contains codepoints that cannot be translated.
You can avoid the failure if you specify a substitution character to replace non-translatable characters. For details on how to ask for character substitution, see SBSUB and SBSUBCHAR as FTP.DATA statements in the z/OS Communications Server: IP Configuration Reference and as parameters on the SITE command in z/OS Communications Server: IP User's Guide and Commands. If substitution occurs during the transfer, the client receives the following reply:
250
One or more characters were substituted during the transfer.
When substitution occurs at the destination of a data transfer, a subsequent transfer of the resulting data does not produce an exact copy of the original. For example, if you put a file to the server and one or more characters are substituted, the untranslatable characters are overlaid in the server copy with the substitution character. You cannot restore the original file by getting it from the server.