Use msys created SOCKS configuration file selected below

Selecting "Use msys created SOCKS configuration file selected below" allows you to use msys to create SOCKS configuration files for FTP clients.

Click the "New..." button to create a SOCKS configuration file, click the "Edit..." button to modify a selected SOCKS configuration file, and click the "Remove" button to remove the selected SOCKS configuration file from the list.

The first time you select "Use msys created SOCKS configuration file selected below" you will see the following displayed:

"Active SOCKS configuration file: None"

After you have created a SOCKS configuration file, the display will be updated to indicate the Active SOCKS configuration file as the one you just created.

You may create multiple SOCKS configuration files. All FTP clients you create using msys will see the list of all SOCKS configuration files created using msys. Once you have created a SOCKS configuration file using msys, if you create new FTP clients, you can just click on a SOCKS configuration file in the list to make it the client's active SOCKS configuration file.

If there are multiple SOCKS configuration files listed, you can change the active configuration file for a client by clicking on a different SOCKS configuration file in the list. The display of the active SOCKS configuration file will be updated immediately to indicate your new selection.

You can use the "Report..." button at any time to show the complete SOCKS configuration file for a selected entry. This will show you the exact configuration statements and parameters that will be produced by msys during the update phase.

Be aware that selecting an entry from the SOCKS configuration file list will ultimately produce the FTP.DATA client configuration statement SOCKSCONFIGFILE. The SOCKSCONFIGFILE statement's parameter is a fully qualified MVS data set name, which contains the SOCKS configuration file. During the msys update phase, an FTP SOCKS configuration file will be created as a member of a partitioned data set extended (PDSE), which is defined in the Basic settings task. Therefore, the SOCKSCONFIGFILE's parameter will be the name of the PDSE with the SOCKS configuration file name concatenated as the member name. Keep this in mind in case you relocate the SOCKS configuration file.