Use the ENCODING statement in the server and client FTP.DATA to indicate the type of data encoding on the network. You can also use the SIte and LOCSIte subcommands to set this keyword.
- Server
- Specifies to the server whether to use single or double-byte code pages.
- Client
- Specifies to the client whether to use single or double-byte code pages.
Syntax
.-ENCODING SBCS------. >>-+--------------------+-------------------------------------->< '-ENCODING--+-SBCS-+-' '-MBCS-'
Parameters
- SBCS
- Specifies single byte encoding. Code pages are specified by way of the SBDATACONN statement. This is the default value.
- MBCS
- Specifies multibyte encoding. Code pages are specified by way
of the MBDATACONN statement.
Rule: The data transfer Type must be ASCII to enable multibyte translation when ENCODING=MBCS is set.
Tip: The type is always ASCII when the client initially logs into the server.
Server
- The data transfer Type remains ASCII until the server receives a Type command from the client
- You can send a STAT command to the server to verify the Type setting by issuing the stat subcommand from the z/OS® FTP client, or by issuing a QUOTE STAT command from any FTP client.
Client- Certain subcommands, such as TYPE, BIG5, and others, change the data transfer Type.
- You can use the LOCSTAT subcommand to verify the Type setting.
- Use the TYPE subcommand to restore Type to ASCII
Examples
To indicate that data encoding
was specified using MBDATACONN statement, use the following code:
ENCODING MBCS