Use the SOCKSCONFIGFILE statement to identify the SOCKS server configuration file the FTP client uses to determine which FTP servers require SOCKS protocols.
Parameters
- file-path
- The z/OS® UNIX absolute pathname or the fully qualified MVS™ data set name of the SOCKS configuration file. In accordance with the convention for absolute pathnames, a z/OS UNIX pathname must begin with a slash (/) character. Any file path not beginning with a slash character is considered a fully qualified MVS data set name.
Examples
To direct the client to use the file /etc/ftp/socks.conf for the SOCKS server configuration, specify the following code:
SOCKSCONFIGFILE /etc/ftp/socks.confTo
direct the client to use the data set 'socks.config' for the SOCKS
server configuration, specify one of the following code:
SOCKSCONFIGFILE socks.configSOCKSCONFIGFILE 'socks.config'Usage notes
- If no SOCKSCONFIGFILE statement is specified, the client does not use SOCKS protocols during connection establishment.
- If the client is connecting to an IPv6 node, the client does not use SOCKS protocols during connection establishment.
- The server ignores the SOCKSCONFIGFILE statement.