X-no-Archive:yes
FWIW, the following is from IBM's "TCP/IP V3R2 for MVS: User's Guide", at
<http://www.s390.ibm.com:80/bookmgr-cgi/bookmgr.cmd/BOOKS/EZAA2003/1%2e3%2e7
?SHELF=EZA0BK11>. I know it's still not the RFCs, but at least if HP ARPA
FTP has it wrong, it has plenty of company on the broad way (that leads to
destruction).
| AScii             | Sets the transfer type to ASCII
| Binary            | Sets the transfer type to IMAGE
| EBcdic            | Sets the transfer type to EBCDIC

Campbell Fethers pointed out that one can use SAMBA to upload patches.
Perhaps someone else can answer this particular case. For users who have
direct access to the patches from their 3000 (without needing to go thru a
PC as an intermediary), I am not aware that a smbclient get is an option.
Perhaps it could be.

Our primary use of such ftps are for production file transfers (where the
files are reasonably large and speed counts), which are then copied to
another area, under /MMM/DD date-named directories, where these are then
available via SAMBA for researching production questions. I imagine that
others are using ftp for serving up web pages (we do use SAMBA for this) or
Java code. In the limited benchmarking I have done, ftp get does seem to be
about eight to ten percent faster than smb-aware copying, either smbclient
get, or the NT ResKit's robocopy (uploading from the PC). YMMV.

Greg Stigers
http://www.cgiusa.com