On Thu, 26 Jul 2012 10:37:28 -0500, McKown, John wrote: > >No. sftp uses a separate SSH "subsystem" which does not do the code >translation. IIRC, sftp as distributed by IBM only does a binary transfer. The >Dovetailed Technologies enhancments to z/OS sftp allows for code translation. >And, in addition, allows transfers to/from z/OS legacy data sets and access to >the JES SPOOL (get output and put, as in submit, jobs). > Thanks. I was unaware of that.
>> ssh remote-host "cd wherever && tar -cf - ." | tar -xvf - >> >> With EBCDIC, I'd need an iconv in the pipe. > >You mean to do the equivalent of a "binary" transfer? I don't think you'd >succeed. I almost never use ssh for file transfer. I guess because I find scp >easier, for me. > I take that as a challenge. >scp /wherever/* user@remote-host:/wherever/ > >On Linux, I've also done: > >cd /wherever; echo -e 'cd /wherever\nmput *\nquit\n' | sftp user@remote; cd - > But will either of those do a recursive copy of an entire directory hierarchy? >You cannot do ssh under TSO OMVS. That is documented by IBM in the OpenSSH >manual. The reason given on one of the forums was the fact that there is no >way to "nodisplay" what you type in for the passphrase or password when >running under TSO OMVS. > Another challenge? If my Rexx works from the ISPF command line, I'd hardly expect it to fail from TSO OMVS. Need to try. I believe ftp (not sftp) successfully masks the password from the TSO OMVS command line. There's a Rexx utility, getpass(prompt) to do that. But years ago I submitted a PMR that neither "stty -echo" nor the underlying syscall masked the command line for password entry. IBM fixed stty but not the underlying syscall. Go figger. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
