Yes, it's easy to copy/paste a text key using a terminal emulator and
then vi or whatever on the target. But I tended to avoid using a 3270
OMVS connection on USS and instead almost always connected to the
mainframe using SSH. So in my case that would have been a PuTTy to
PuTTy copy/paste, using the vi editor.
More often I'd use scp because I was most likely creating a new
authorized_keys file on the target machine anyway. In addition, running
scp from the mainframe would test the IP connection, test the target id,
and also ask me if it's ok to copy the target's host key into the
mainframe known_hosts file. Skipping that last item can cause some head
scratching when you try to run a batch sftp.
You're far more advanced than me when it comes to stringing unix
commands together, so let me look closer:
cp - copy the z/OS member I want to transfer to the data stream.
ssh - receive that data stream and connect to Tom@Linux and then issue
the cat command with > that will take that data stream and poke it in
Linux.file.
I didn't know you could do that with streams across ssh - pretty
interesting!
On 9/1/2022 9:06 AM, Paul Gilmartin wrote:
On Thu, 1 Sep 2022 07:33:57 -0700, Tom Brennan wrote:
...
But like you say (and if nothing has changed over the years), you need
to setup keys.
Ssh-keygen makes it easy. The keys are stored as text files. It ought
to be possible to Copy from a Vista OMVS window and Paste to
a Linux xterm ssh window.
And sftp only worked with USS files so an OCOPY or
similar was needed for z/OS datasets, and some temp USS space.
How about:
/bin/cp [options] "//'MVS.DATA.SET(MEMBER)'" | ssh -f Tom@Linux "cat
>Linux.file"
Unconditional IBM-1047 -> ISO8859-1 conversion. If you want it not to do that,
insert
an iconv filter on the z/OS end.
Or try to get Purchasing to approve Co:Z.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
