sftp on openvms

[Joseph Huber_1]

>>
When i try sftp user@host it is throwing the below error:
Usage: /sys$system/tcpip$ssh_ssh2 [POSIX or GNU style options] -f progfile [--] file ...
<<

The "usage" response shows again some syntax error/wrong arguments.
Would You show us what You REALLY type as the command?
Also version of system and TCPIP software:
TCPIP SHOW VERSION
sftp -v
show symbol sftp
show process /parse_style

[CHANDRASEKARAN S]

I types the below:


$sftp ezps@69.94.86.93
Usage: /sys$system/tcpip$ssh_ssh2 [POSIX or GNU style options] -f progfile [--] file ...
/sys$system/tcpip$ssh_ssh2 [POSIX or GNU style options] [--] "program" file ...
POSIX options: GNU long options:
-f progfile --file=progfile
-F fs --field-separator=fs
-v var=val --assign=var=val
-m[fr]=val
-W compat --compat
-W copyleft --copyleft
-W copyright --copyright
-W help --help
-W lint --lint
-W posix --posix
-W source=program-text --source=program-text
-W usage --usage
Warning: child process (/sys$system/tcpip$ssh_ssh2) exited with code 44.


%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation

*****************************************

$TCPIP SHOW VERSION

HP TCP/IP Services for OpenVMS Alpha Version V5.6 - ECO 3
on an AlphaServer GS320 6/1224 running OpenVMS V8.3

$
$sftp -v
Sftp2/SFTP2.C:5183: CRTL version (SYS$SHARE:DECC$SHARE ident) is: V8.3-01

SshFileCopy/SSHFILECOPY.C:1354: Making local connection.
Ssh2SftpServer/SSHFILEXFERS.C:2120: Received SSH_FXP_INIT
Ssh2SftpServer/SSHFILEXFERS.C:2165: version is 999
Ssh2SftpServer/SSHFILEXFERS.C:2227: Sending SSH_FXP_VERSION with sftp-version@openvms.hp.com as 3
SshFileXferClient/SSHFILEXFERC.C:1432: ssh_file_client_receive_proc: coming in with extension data, OpenVMS host
SshFileXferClient/SSHFILEXFERC.C:1478: vms_plus_sftp_version = 3
SshFileCopy/SSHFILECOPY.C:1293: Connection to local, ready to serve requests.
Sftp2/SFTP2.C:822: Connection ready.
SshReadLine/SSHREADLINE.C:3662: Initializing ReadLine...
sftp>
sftp>
sftp> exit
SshReadLine/SSHREADLINE.C:3728: Uninitializing ReadLine...


$

[Joseph Huber_1]

Although my version is older, it gets a "usage" response only if the command-line is really wrong.
And in Your case it gets an error as soon as You have a user@host argument.
My suspicion still is: You have a DCL symbol "sftp" defined,
what does "SHOW SYMBOL SFTP" return ?

[CHANDRASEKARAN S]

$SHOW SYMBOL SFTP
%DCL-W-UNDSYM, undefined symbol - check validity and spelling

[Steven Schweda]

> I need to connect to an IP through SFTP
> from VMS.[...]

1. If you have your own question, then start
your own thread. Don't wake some old, dead,
unrelated thread.

> HP TCP/IP Services for OpenVMS Alpha Version V5.6 - ECO 3
> on an AlphaServer GS320 6/1224 running OpenVMS V8.3

2. Around here:

alp $ tcpip show vers

HP TCP/IP Services for OpenVMS Alpha Version V5.6 - ECO 5
on a COMPAQ Professional Workstation XP1000 running OpenVMS V8.3

alp $ sftp "-V"
alp$dka0:[sys0.syscommon.][sysexe]tcpip$ssh_sftp2.exe: SSH Secure Shell OpenVMS
(V5.5) 3.2.0 on COMPAQ Professional Workstation - VMS V8.3

alp $ sftp sms@alp-l

@ SYS$MANAGER:ANNOUNCE.TXT
sftp> pwd
ALP$DKA0:[SMS]
sftp> quit


alp $ sftp sms@10.0.0.9

@ SYS$MANAGER:ANNOUNCE.TXT
sftp> pwd
ALP$DKA0:[SMS]
sftp> quit


alp $ sftp -v fred fred
Too many arguments.
Usage: sftp2 [-D debug_level_spec] [-B batchfile] [-S path] [-h]
[-V] [-P port] [-b buffer_size]
[-4] [-6] "[-C]" [-o option_to_ssh2]
[user@]host[#port]


Have you tried installing a newer TCPIP ECO?

[Joseph Huber_1]

Well mine seems to behave much different,
especially to automatically connect to the local host if asking the version in
sftp -v , which actually is "sftp -V".
Hope somebody with the combination VMS8.3/TCPIP 5.6 can reproduce something like that.

Meanwhile use debugging/verify:

sftp -"v" user@host !observe the string quotes!

to see more disgnostic revealing the point at which the error occurs.

[Hoff]

CHANDRASEKARAN S:

In no particular order...

Ensure that the ssh client and ssh server are appropriately started via TCPIP$CONFIG.COM

Failure to start the appropriate client and server components has an unfortunate and long history of tossing obscure errors.

Patch to current; V5.6 ECO 2 is old.

Ensure the process quotas and process environment are sufficient. Details on minimum quotas should be in the manual, and you'll likely need TMPMBX and NETMBX minimally.

Test connections into the target server from another box. See if this is local or a server error.

Remove any DECC* logical names that might be around in the process or job context. Sufficiently odd settings for these can trigger errors in most any C application.

And I'm seeing completely different "usage" diagnostics with V5.6 ECO 5, so definitely roll forward to ECO 5.

[Steven Schweda]

> sftp -"v" user@host !observe the string quotes!

Quoting "-v" is not required. Quoting "-V"
probably _is_ required. (As shown above.)

[Joseph Huber_1]

>> Quoting "-v" is not required. Quoting "-V"
probably _is_ required.

So I keep quiet. Seems there are so many changes between TCPIP 5.4 and 5.6.
On my 5.4 sftp is a DCL verb, and both unquoted -V and -v result in "show version".
Only -"v" results in the desired "verbose".

[The Brit]

It would be nice to see the output from

$ sftp "-V"

Dave