Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Behavior of SFTP lcd command (v5.6 eco2 & v5.4 eco6)

 
stephen hill_6
Occasional Visitor

Behavior of SFTP lcd command (v5.6 eco2 & v5.4 eco6)

Hi, we have encountered an issue when moving our command procedures from a VMS v7.3-2 system to a v8.3 system where LCD command fails. The remote server is a linux machine and the VMS v7.3-2 (tcpip v5.4 eco2) works fine, but the VMS 8.3 cluster (tcpip v5.6 eco2) fails when using VMS syntax.

Ex:
8.3 system
$ SFTP xeroxpal@10.173.116.60
sftp> lcd pal_hfs$:[xerox_postcar
CD failed.
/USER$/irm/vhamachillsg
sftp> lcd pal_hfs$/xerox_postcard/pcard
/PAL_HFS$/xerox_postcard/pcard
sftp> exit



(Thanks for any guidance you gave provide.)


2 REPLIES
Steven Schweda
Honored Contributor

Re: Behavior of SFTP lcd command (v5.6 eco2 & v5.4 eco6)

> [...] we have encountered an issue [...]

Is that anything like a problem?

> sftp> lcd pal_hfs$:[xerox_postcar

Should we be troubled by the apparent
truncation here?

Around here:

ALP2 $ tcpip show version

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

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


ALP2 $ sftp sms@alp
sms@alp's password:
sftp> lcd ALP2$DKB300:[CD
Warning: chdir(ALP2$DKB300:[CD) returned errno = 2
PWD failed.
sftp> lcd ALP2$DKB300:[CDR]
ALP2$DKB300:[cdr]
sftp> quit


Mine seems to work as expected.

(Am I missing something, or do we need to
assume/deduce that you're on Alphas?)
Art Wiens
Respected Contributor

Re: Behavior of SFTP lcd command (v5.6 eco2 & v5.4 eco6)

"Is that anything like a problem?"

I think it goes:

If you're doing it wrong and it doesn't work, it's an issue.

If you're doing it right and it doesn't work, it's a problem.

"Thanks for any guidance you gave provide"

It would probably help more if you could provide the actual procedure and the actual output ... I assume the example you show is a manual attempt and it's not typed correctly as Steven pointed out.

If your typing for us what you're seeing in a log, then perhaps your command procedure relies on some symbol sustitutions which aren't defined on the 8.3 environment and the command isn't being fully populated when it executes ie. dropping the d.pcard] from the line. Is it a procedure which is being dynamically created by another procedure?

Cheers,
Art