> scp -q -i ~ken/.identity -B file remote:file > What's so hard? FTP may be the lowest common denominator, > but it's not the only solution.
I agree, but... NJE support is built in to z/OS. SCP isn't, and the ssh port for USS is pretty precarious. SSH/SCP aren't supported at all on VM or VSE (w/o 3rd party tools). FTP or NJE are what you have if you have to play nice with the rest of the IBM family. . SCP also isn't integrated at all into spooling and output management. I've been toying with the idea of writing a IPP server/client for CMS and friends -- it wouldn't be too hard to expand that to support file transfer as well. IPP supports a "file:" class. I suppose that would be a nice enhancement request for RSCS: IPP support. Given that, most of the drawbacks of printing from the various IBM operating systems to distributed printers would just go away (and we'd regain a lot of nice function that LPR just doesn't support). -- db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
