Jim,
The two primary non-proprietary protocols and IBM products are:
- FTPS (TLS). This is supported by z/OS Communications Server.
- SSH SFTP. This is supported by z/OS Ported Tools - OpenSSH.
FTPS pros -
Full dataset support by z/OS CS
Generally, better native z/OS features than Ported Tools SSH
FTPS cons -
Uses multiple sockets which can be tricky wrt firewalls, NAT routers, etc
Requires compatible FTPS server
SFTP pros -
Single socket connection, much more firewall friendly
SSH/SFTP tends to be more widely available on partner *nix systems than
FTPS
SFTP cons -
Ported Tools version of OpenSSH doesn't support MVS datasets, SMF, etc.
Other options -
- We offer a free extension to Ported Tools OpenSSH that adds MVS dataset
support and SMF logging to SFTP.
- We also offer a free proxy tool that can be used to tunnel regular FTP
over an SSH connection.
- SSH Communications offers their own completely separate SSH/SFP product
("Tectia").
Kirk Wolf
Dovetailed Technologies
http://dovetail.com
PS> Are you interested in more information on z/OS SSH SFTP ? We plan on
offering a free webinar on Ported Tools OpenSSH and SFTP. Please drop me an
email if you are interested and I'll add you to announcement list when it is
available.
On Tue, Mar 31, 2009 at 9:24 AM, Jim McAlpine <[email protected]>wrote:
> What protocols are available to enable secure file transfer with z/OS being
> the client. I've RTFM but not found a great deal and the archives are not
> helping me very much.
>
> Jim McAlpine
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
