MBCS support in the FTP server is provided for the following code
page pairs:
| Support for: |
TYPE command |
File system code page |
Network transfer code page |
|---|
| Chinese standard GB18030 |
Not applicable |
IBM-1388 or UTF-8 |
IBM-5488 |
| BIG5 |
TYPE B 8 |
IBM-937 |
IBM-950 or BIG5 |
| EUCKANJI |
TYPE B 2 |
IBM-930 |
IBM-eucJP |
| JIS78KJ (JISROMAN |
TYPE B 4 R |
IBM-930 |
IBM-5053 |
| JIS78KJ (ASCII |
TYPE B 4 A |
IBM-939 |
IBM-5055 |
| JIS83KJ (JISROMAN |
TYPE B 3 R |
IBM-930 |
IBM-5052 |
| JIS83KJ (ASCII |
TYPE B 3 A |
IBM-939 |
IBM-5054 |
| KSC5601 |
TYPE B 6 |
IBM-933 |
IBM-949 |
| SCHINESE |
TYPE B 9 |
IBM-935 |
IBM-1381 |
| SJISKANJI |
TYPE B 1 |
IBM-930 or IBM-939 |
IBM-932 or IBM-eucJC |
| TCHINESE |
TYPE B 7 |
IBM-937 |
IBM-948 |
| UNICODE |
Not applicable |
UTF-8, UTF-16 |
UTF-8, UTF-16, UTF-16BE, and UTF-16LE |
Rules: - ENCODING must be specified as MBCS, either in FTP.DATA or on a
SITE command.
- The data type must be ASCII.
- The file structure must be FILE (not RECORD), and the transfer
mode must be STREAM (not BLOCK or COMPRESS).
- The FTP file type must be SEQ (not JES or SQL).
- If the file is transferred to or from an MVS™ data set, the record format of the data set
must be V, VB, or U.
- If a file is transferred outbound and is an MVS data set with record format V or VB, the
request for RDWs is not allowed.
- Translation of ASA or machine control characters is not allowed.
- MBCS can be used as a migration path for the DBCS languages listed
that have an associated TYPE B x command.
Restriction: The DBCS languages can be migrated to the MBCS
support only if they do not use the following parameters on the TYPE
B
x command:
- S A
- SOSI ASCII characters X'1E' and X'1F' in the ASCII data stream
- S E
- SOSI EBCDIC characters X'0E' and X'0F' in the ASCII data stream
- S S
- SOSI SPACE characters X'20' and X'20' in the ASCII data stream
- N
- No SOSI characters in the ASCII data stream and none written to
the file system