cancel
Showing results for 
Search instead for 
Did you mean: 

sftp issues

 
Jason_429
Occasional Advisor

sftp issues

Does anyone know if sftp is going to act like a native vms utility instead of a nix port in future releases ?

Some examples
-Case sensitive
-No DIR or SHOW DEF command only ls and pwd ect

These are not a big deal, but it can get annoying at certain times.
----------------------------------------------

Here are some issues i encounter using sftp. I do not know if some settings are wrong but i am confused on the way sftp handles some requests.

All these examples are between the following two machines.

Client - VMS 8.3 TCPIP v5.6
Server - VMS 8.3 TCPIP v5.6- eco 4

I have two system logicals set up on the server side.
"FIX" = "DQB0:[FIX]" (LNM$SYSTEM_TABLE)
"BAS" = "DQB0:[BAS]" (LNM$SYSTEM_TABLE)

The protections/ownerships on the directories are the same. I am using a privileged account on both machines.

sftp> cd fix
DQB0:[FIX]
sftp> cd bas
CD failed.
DQB0:[FIX]

I can access the bas logical using the full path.
sftp> cd dqb0:[bas]
dqb0:[bas]
sftp>
--------------------

I also seem to have an 'ls' issue

(VMS dir command)
Directory DQB0:[FIX]
T.T;6 T.T;5

(sftp ls command)
sftp> ls fix:t.t
sftp>

The ls command, after thinking for a while just returns me back to the sftp prompt
---------------------------------------------

I also can not issue a get/put using a logical. I have to change to the directory i want to get/put from/to. Is this a sftp security feature ?

sftp> get fix:t.t
SshFCRecurse/SSHFC_RECURSE.C:362: File is "raw", and it needs to be parsed.
SshFCRecurse/SSHFC_RECURSE.C:297: Received error `syserr: no such file or direc.
fcr_parse_raw: fix/fix:t.t (src): no such file (server msg: 'syserr: no such fi)
SshFCTransfer/SSHFC_TRANSFER.C:2321: File list has 0 files.

This throws a file not found error, when i know the file exists.

It would be nice to be able to use logicals like you can in ftp.

For example:
ftp>get logical:file.ext logical:file.ext
Works on ftp where it doesn't on sftp
2 REPLIES 2
John Gillings
Honored Contributor

Re: sftp issues

Jason,

Log a case with your local customer support centre, requesting enhancements.

but the way HP seems to be treating OpenVMS these days, I wouldn't hold my breath :-(
A crucible of informative mistakes
Steven Schweda
Honored Contributor

Re: sftp issues

> Does anyone know if sftp is going to act
> like a native vms utility instead of a nix
> port in future releases ?

Of the future, it's hard to be certain, but
my money would be on it continuing to act
like what it is, namely UNIX software ported
(none too well) to VMS. My favorite:

alp $ sftp alp-l

@ SYS$MANAGER:ANNOUNCE.TXT
sftp>


> -No DIR or SHOW DEF command only ls and pwd
> ect

That's "etc.", as in "et cetera". In old
books, where people still knew what they were
abbreviating, you may see "et c.", which I
find charming. In the race for most
annoying, it's a tie between people who say
"eck cetera" and people who say "and et
cetera". ("And eck cetera" beats both of
those, of course.) But I digress.

I've given up, and adapted. I don't know why
your apparently similar "fix" and "bas" don't
behave the same, but I have no obvious
trouble when I use UNIX-like path notation.
For example:

ALP $ show logical /system aftp*

(LNM$SYSTEM_TABLE)

"AFTP" = "HOME_ANON:[ANONYMOUS]"
"AFTP_ROOT" = "HOME_ANON:[ANONYMOUS.]"

sftp> ls -l /aftp/announce.txt
-rwxr-xr-x 1 4 1 41 Mar 12 2005 ANNOUNCE.TXT;2*
sftp> ls -l /aftp_root/info-zip/os.sh
-rwxr-xr-x 1 4 1 1936 Apr 5 0:34 OS.SH;2*

When (imprisoned) in Rome, ...

I don't expect VMS file specs to work in this
environment, so I don't even try. Call me
fatalistic.