TYpe subcommand

Purpose

Use the TYpe subcommand to set the data transfer type for the client and server simultaneously with one command. FTP supports the ASCII, EBCDIC, image (binary), UCS-2, and two DBCS data transfer types.

Format


         .-A---------------------------------.   
>>-TYpe--+-B--+----------------------------+-+-----------------><
         |    | .-1-.                      | |   
         |    +-+-2-+--+----------+--+---+-+ |   
         |    | +-5-+  |    .-A-. |  '-N-' | |   
         |    | +-6-+  '-S--+---+-'        | |   
         |    | +-7-+       +-E-+          | |   
         |    | +-8-+       '-S-'          | |   
         |    | '-9-'                      | |   
         |    |        .-A-.               | |   
         |    '-+-3-+--+---+--+---+--------' |   
         |      '-4-'  '-R-'  '-N-'          |   
         +-E---------------------------------+   
         +-F--+---+--------------------------+   
         |    '-1-'                          |   
         +-I---------------------------------+   
         |      .-B-.                        |   
         '-U 2--+---+------------------------'   
                '-L-'

Parameters

A

Sets the transfer type as ASCII. Specifying the ASCII transfer type has the same effect as using the AScii subcommand. When the data transfer type is ASCII, FTP translates outgoing files to ASCII before sending them, and translates incoming files from ASCII to the file system code page before storing them. ASCII is the default transfer type.

B

Sets the transfer type as DBCS. Specifying the B transfer type with the appropriate options has the same effect as using the BIG5, EUckanji, HAngeul, JIS78kj, JIS83kj, Ksc5601, SJiskanji, SChinese, or TChinese subcommands. If B is specified alone, the second type parameter defaults to 1 and current transfer type is changed to Shift JIS kanji.

When you transfer double-byte data, the currently active SBCS translation table is used for SBCS characters in the data set. If necessary, use the SIte/LOCSIte SBDataconn or SIte XLate FTP subcommand to select an alternate SBCS translation table that is appropriate for your data before transferring your double-byte data.

B 1: Changes current transfer type to Shift JIS kanji.
B 2: Changes current transfer type to Extended UNIX Code kanji.
B 3: Changes current transfer type to JIS 1983 kanji.
B 4: Changes current transfer type to JIS 1978 kanji.
B 5: Changes current transfer type to Hangeul.
B 6: Changes current transfer type to Korean Standard Code KSC-5601, 1989 version.
B 7: Changes current transfer type to Traditional Chinese (5550).
B 8: Changes current transfer type to Big-5.
B 9: Changes current transfer type to Simplified Chinese.

S

Transferred data contains shift-out and shift-in delimeters.

If S is specified alone, the second parameter defaults to A. Shift-out and shift-in characters X'1E' and X'1F' are used.

The S parameter can be used to control the use of shift-out (SO) and shift-in (SI) characters during DBCS data transfer for Big5, SChinese, Shift-JIS kanji, EUC kanji, Hangeul, KSC-5601, and TChinese.

If Sosi is not specified at all, shift-out or shift-in characters are not used in the transferred data.

S A: Use shift-out and shift-in characters X'1E' and X'1F' to delimit DBCS strings in the transferred data.
S E: Use shift-out and shift-in characters X'0E'and X'0F' to delimit DBCS strings in the transferred data.
S S: Use ASCII spaces (X'20') as shift-out and shift-in characters to delimit DBCS strings in the transferred data.

A

Use ASCII shift-in escape sequence ESC ( B. This is the default. (Used for DBCS data types JIS 1983 kanji and JIS 1978 kanji only.)

R

Use JISROMAN shift-in escape sequence ESC ( J. (Used for DBCS data types JIS 1983 kanji and JIS 1978 kanji only.)

N

Indicates that the transfer is to be pure DBCS data (data with no SBCS characters) and that the data is to be transferred to or from EBCDIC DBCS data that contains no shift-out or shift-in delimiters.

When data is transferred from the EBCDIC host, the entire data set is assumed to be EBCDIC DBCS with no SO/SI characters in the data. The data is then converted to the required ASCII type and if any SO/SI option has been specified for the transferred data then the corresponding SO/SI characters are used to delimit the ASCII DBCS strings.

When transferring data to the EBCDIC host, no SO/SI characters are inserted, and if any SO/SI option is specified for the transferred data, the corresponding SO/SI characters are removed from the ASCII data and not replaced at the host. The length of data might change during transfer to and from the EBCDIC host when pure DBCS is specified with any SO/SI option. When pure DBCS is specified by itself, the length of data does not change. If N is not specified, the shift-out or/shift-in characters X'0E' and X'0F' are used at the host.

E

Sets the transfer type as EBCDIC. Specifying the EBCDIC transfer type has the same effect as using the EBcdic subcommand. The EBCDIC transfer type is intended for efficient transfer between hosts that use EBCDIC for their internal character representation.

F

Sets the transfer type as EBCDIC IBM® kanji. Specifying the IBM kanji transfer type has the same effect as using the Ibmkanji subcommand.

F 1: Change current transfer type to IBM (EBCDIC) kanji.

I

Sets the transfer type as image (binary). Specifying the image transfer type has the same effect as using the BINary subcommand. With the image transfer type, data is sent as contiguous bits, packed into 8-bit bytes. The image transfer type is used for the efficient storage and retrieval of data sets or files, and for the transfer of binary data.

U 2

Sets the transfer type to Unicode UCS-2. TYpe U 2 has optional parameters:

B: Specifies big-endian byte order for Unicode encoding. This is the default.
L: Specifies little-endian byte order for Unicode encoding.

Examples

Transfer text data to another host:

  User:    ascii
System:      >>>TYPE A
             200 Representation type is ASCII.
             Command:

Transfer binary data to another host:

  User:    type i
System:      >>>TYPE I
             200 Representation type is IMAGE.
             Command:

Transfer text data from an EBCDIC host to an EBCDIC host:

  User:     type e
System:      >>>TYPE E
             200 Representation type is Ebcdic NonPrint
             Command:

Transfer binary data from an EBCDIC host to an EBCDIC host:

  User:     type i
System:      >>>TYPE I
             200 Representation type is Image.
             Command:

Set the transfer type to JIS 1983 kanji using the JISROMAN shift-in escape sequence ESC ( J:
```
TYPE B 3 R
```
Set the transfer type to Shift-JIS kanji using the EBCDIC SO/SI characters X'0E'/X'0F' in the transferred date:
```
TYPE B 1 S E
```

Usage

If no Sosi option is specified by the TYpe command for BIG5, SChinese, EUckanji, HAngeul, Ksc5601, SJiskanji, or TChinese, standard DBCS control is used for the data transfer. This means that no SO/SI characters are placed in the ASCII data when transferring from the (EBCDIC) host to ASCII and the value of each ASCII character is used to determine if it is a single-byte character or part of a double-byte character when transferring to the host. For JIS 1983 kanji and JIS 1978 kanji, three-character escape sequences are always used to delimit DBCS strings in mixed SBCS/DBCS ASCII data. These escape sequences cannot be altered by using the S, S A, S E, or S S parameters.
If no Sosi option is specified, the length of data might change as it is transferred to or from the EBCDIC host since EBCDIC DBCS types on the host contain SO/SI characters in mixed SBCS/DBCS data to determine which characters are part of a DBCS string. Any of the above SO/SI options (S, S A, S E or S S) can be used for mixed SBCS/DBCS data so that the length of data does not change when transferred to or from the EBCDIC host. Use of three-character escape sequences for JIS 1983 kanji and JIS 1978 kanji means that the length of data for these types always changes when transferring mixed SBCS/DBCS data to or from the EBCDIC host.
Use ASCII spaces as SO/SI characters in the transferred data only for transfer from the EBCDIC host. Data can be transferred to the host when using this option but care must be taken as each ASCII space is interpreted as a shift-out or shift-in character and is replaced with the corresponding SO/SI character on the host.

Context

For more information about transfer methods, see Table 1.