SJiskanji subcommand

Purpose

Use the SJiskanji subcommand to change the data transfer type to SJISKANJI.

MVS™ FTP uses the same SBCS translate table for single-byte or double-byte data transfers. If you require an alternate SBCS table for a double-byte transfer, use the SIte/LOCSIte SBDataconn or SIte XLate subcommand to have the server (or client) change the SBCS translation for the data connection.

Format


>>-SJiskanji---------------------------------------------------->

>--+---------------------------------------------------+-------><
   '-(--+----------------------+--+------+--+--------+-'   
        |       .-Ascii------. |  '-NOSo-'  '-NOType-'     
        '-Sosi--+------------+-'                           
                +-+--------+-+                             
                | '-Ebcdic-' |                             
                '-+-------+--'                             
                  '-Space-'

Parameters

Sosi

Transferred data contains the shift-out and shift-in characters specified by one of the following parameters — Ascii, Ebcdic or Space. If no parameter is specified, ASCII is used as the default.

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

Ascii: When combined with the Sosi parameter, causes shift-out and shift-in characters X'1E' and X'1F' to be used to delimit DBCS strings in ASCII data.
Ebcdic: When combined with the Sosi parameter, causes shift-out and shift-in characters X'0E' and X'0F' to be used to delimit DBCS strings in ASCII data.
Space: When combined with the Sosi parameter, causes shift-out and shift-in characters X'20' and X'20' (ASCII spaces) to be used to delimit DBCS strings in ASCII data.

NOSo

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

NOType

Suppresses the sending of the corresponding TYpe command to the server. Use this parameter when translation is to be done by the FTP client only.

Examples

To cause the FTP client to change its transfer type to Shift JIS kanji, without sending a TYpe command to the FTP server, use:

SJISKANJI (NOTYPE

The server in this example should be set to the ASCII transfer type before the (NOTYPE subcommand is issued.

Usage

The SJiskanji client subcommand is equivalent to the TYPE B 1 server command.
The SJiskanji (Sosi or SJiskanji (Sosi ASCII client subcommands are equivalent to the TYPE B 1 S A server command.
The SJiskanji (Sosi Ebcdic client subcommand is equivalent to the TYPE B 1 S E server command.
The SJiskanji (Sosi SPACE client subcommand is equivalent to the TYPE B 1 S S server command.
The SJiskanji (NOSO client subcommand is equivalent to the TYPE B 1 N server command.

Context

See FTP with traditional DBCS support and Support for MBCS languages for more information.