We regularly use the scp command in batch job on the z/OS side and I have generated the keys in my linux under z/VM system. It is much easier for m e to do it than to teach the cobol developers.
I know that scp uses the ssh protocol but I was hoping that since it does not need more than a linemode session on the local host that it would for k less or invoke less terminal related processes and therefore be easier to port to CMS. It would be nice if there was a straight forward implementat ion of filecopy and command submission wrapped in the ssh protocol, like the pscp and plink commands from PuTTY. /Tom Kern On Thu, 1 Feb 2007 15:44:34 -0500, Richard Troth <[EMAIL PROTECTED]> wrote: >SCP uses SSH under the covers. Your local SCP uses SSH to connect with a >partner SCP. From what I have seen, it does spawn a second process on >the local side, so it's the same SSH command people would execute for >non-SCP work. Multiple processes is cumbersome, and on CMS (OpenVM) is >particularly heavy and can be messy. Though I can see why the authors >would find the implementation easier that way. > >I have never tried switching out what SCP uses for the session layer. It 's >not clear that you can change SCP's use of SSH. The "command at target " >implies that SSH (and SCP) was installed outside of the default command >search, in which case the partner SCP must be fully named. > >Experience with the z/OS SSH package confirms that you can generate your >keys on a Unix system (or Linux or CYGWIN). They're stored as plain >text. > >-- R;
