UTF-8 enabled control connection

You can specify EXTENSIONS UTF8 in the client's FTP.DATA data set to enable the FTP client to use and accept UTF-8 encoding of the control connection. See the z/OS Communications Server: IP Configuration Reference for information about the EXTENSIONS statement. If you code EXTENSIONS UTF8 in the client's FTP.DATA data set, the login sequence is different. Following is an example of logging in to a UTF-8 enabled FTP server when the client has enabled UTF-8 encoding of the control connection.

IBM FTP CS V1R5 
FTP: using TCPCS                                             
Connecting to:   9.67.113.37 port: 21.                       
220-FTPD1 IBM FTP CS V1R4 at vic135, 19:16:11 on 2003-01-15. 
220 Connection will close if idle for more than 5 minutes.   
>>> FEAT                                                     
211- Extensions supported                                    
 UTF8                                                        
 LANG en*                                                    
211 End                                                      
>>> LANG en                                                  
200 - Language is en-US (United States English)              
NAME (9.67.113.37:USER10): 

>>> USER USER10                                                
331 Send password please.                                      
PASSWORD:                                                      
                                                               
                                                               
>>> PASS                                                       
230 USER10 is logged on.  Working directory is "/tmp".         
Command:

The difference is that the client issues the FEAT command during login to negotiate use of UTF-8 on the control connection, as specified in RFC 2640 (see Related protocol specifications). In this example, the FEAT reply indicates the server supports RFC 2640 (UTF8 and LANG keywords), so the client issues LANG to commence UTF-8 encoding of the control connection.

Here is an example of a UTF-8 enabled client logging in to a server which does not support UTF-8 encoding:

IBM FTP CS V1R5 
FTP: using TCPCS                                               
Connecting to:   9.67.113.37 port: 21.                         
220-FTPD1 IBM FTP CS V1R4 at vic135, 19:20:43 on 2001-10-15.   
220 Connection will close if idle for more than 5 minutes.     
>>> FEAT                                                       
211- Extensions supported                                      
 SIZE                                                          
 MDTM                                                          
 REST STREAM                                                   
211 End                                                        
NAME (9.67.113.37:USER10):                                     
                                                               
>>> USER USER10                                                
331 Send password please.                                      
PASSWORD:                                                      
                                                               
                                                               
>>> PASS                                                       
230 USER10 is logged on.  Working directory is "/tmp".         
Command:

The client issued the FEAT command during login because EXTENSIONS UTF8 is coded in FTP.DATA. Since the server FEAT reply did not indicate the server supports RFC 2640, no LANG command was issued by the client. The client will not send UTF-8 encoded data to this server.