venkat kulkarni wrote:
To provide you move detail, I earlier copied id_dsa.pub key from mainframe
to target host authorized_keys file.
So, in place of id_dsa.pub key, will it make difference, if we copy id_dsa
key to target host.
No, that wouldn't help. The public key is what is needed in the remote server's
authorized_keys file.
your .ssh directory : 700
your id_dsa : 600
your id_dsa.pub: 644
remote server .ssh directory : 700
remote server authorized_keys : 600
If key negotiation does indeed work, you will need to remove the " -b -" and
also the sending of the password.
You should try the command line which is embedded in the JCL from inside USS
itself without the JCL.
All that the JCL is doing is sending USS a command line.
Try it interactively in USS if you have not already done so. Make a shell file
in USS that says something like
# myxfer.sh
cat << END password
cd /tmp
ascii
put /tmp/SOME.FILE.NAME some.file.name
END | sftp -v -b - [email protected]
and see if you can execute that successfully right in USS, using the 'bash'
command if you have it, e.g.,
bash ./myxfer.sh
It's 01:40 here in Colorado ... I'm going to bed. Good-night and good luck,
Venkat!
Jack
--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
