Data Type Conversions via FTP when Transferring Files from an AS/400 System

  • B = Shift JIS Kanji (932 CCSID)
  • B 1 = Shift JIS Kanji (932 CCSID)
  • B 2 = Extended UNIX Code Kanji (5050 CCSID)
  • B 3 = JIS 1983 using ASCII shift-in escape sequence (5054 CCSID)
  • B 3 A = JIS 1983 using ASCII shift-in escape sequence (5054 CCSID)
  • B 3 R = JIS 1983 using JISROMAN shift-in escape sequence (5052 CCSID)
  • B 4 = JIS 1978 using ASCII shift-in escape sequence (5055 CCSID)
  • B 4 A = JIS 1978 using ASCII shift-in escape sequence (5055 CCSID)
  • B 4 R = JIS 1978 using JISROMAN shift-in escape sequence (5053 CSID)
  • B 5 = Hangeul (CCSID 934)
  • B 6 = Korean Standard Code KSC-5601, 1989 version (CCSID 949)
  • B 7 = Traditional Chinese (CCSID 938)
  • C = Allows the user to set the transfer type to any CCSID (coded character set identifier) which is installed on the system. The CCSID # must follow C.
  • E = Specifies the transfer type as EBCDIC.  This has the same effect as the EBCDIC subcommand.  No vertical format control is associated with the file.  Only the default format NON PRINT is supported for EBCDIC.  The EBCDIC transfer type is intended for efficient transfer between systems that use EBCDIC for their internal character representation.
  • F = IBM EBCDIC Kanji (CCSID 5035)
  • F 1 = IBM EBCDIC Kanji (CCSID 5035)
  • I = Specifies the transfer type as image.  This has the same effect as the BINARY subcommand.  With the image transfer type, data is sent as a string of bits, packed into 8-bit bytes.  The image transfer type is used for efficiently storing and retrieving files and for transferring binary data such as object code.
Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case