File Transfer protocols are being implemented as customer demand requires them. With this option, use the number of the host defined in the web.config, not the host's name. So, if "Insure" is host2, you would use FileXfer_for_Host2 to identify the available file transfer protocols for the Insure (host2) FVTerm host sessions.
Example:
<add key="FileXfer_for_Host2" value="IND$FILE"/>
Available options:
IND$FILE |
For IBM Mainframes -- available as a additional feature. When this is set for a host, when the user connects to a session, the |
file transfer icon will appear in the user's FVTerm actions. Clicking on this will provide the available options including selection of DFT or CUT mode. Users are expected to be familiar with the use of IND$File and if on a TSO session, at a TSO command prompt to initiate the file transfer(s).
The future, possible options, which can be separated with a vertical bar, are planned to include:
FTP |
For IBM Mainframes, UNIX, Linux, AS400 / iSeries / IBM i and other systems supporting FTP -- note that FTP uses a separate connection from the active terminal connection and requires that the user have the necessary authority to run FTP. |
FTPS |
For any system supporting FTP over SSL |
SFTP |
Uses Secure FTP -- Only available on UNIX/Linux hosts connected using the SSH protocol. Will use the existing Bitvise SSH license. |
Kermit |
For UNIX/Linux hosts, based on Columbia University Kermit |
ZModem |
For UNIX/Linux hosts-- will use ZModem protocol using code purchased from OMEN Technologies |
XModem |
For UNIX/Linux hosts-- will use the XModem protocol using code purchased from OMEN Technologies |
YModem |
For UNIX/Linux hosts-- will use the YModem protocol using code purchased from OMEN Technologies |
