Doesn't handle MVS pathnames terribly well

[gregglind]

Unlike 2.2.8, VMS support in 3.0.0 beta 2 on Windows XP
SP2 seems incomplete.

Entering the same command on the "Remote Site" field
yields different results (as shown in the log below
where I had entered:

DKA4:[GENETIC_EPI_PATHVOL]

each time.

Command: PASS
Response: 230 User logged in.
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "GENERAL:[THISUSER]" is current directory.
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CWD DKA4:[DKA4:[GENETIC_EPI_PATHVOL]
Response: 550-Failed to set default directory to
DKA4^:[DKA4^:[GENETIC_EPI_PATHVOL^{].
Response: 550 invalid directory
Error: Failed to retrieve directory listing
Status: Retrieving directory listing...
Command: CWD DKA4:[DKA4:[GENETIC_EPI_PATHVOL]
Response: 550-Failed to set default directory to
DKA4:[DKA4:[GENETIC_EPI_PATHVOL].
Response: 550 file specification syntax error
Error: Failed to retrieve directory listing
Status: Retrieving directory listing...
Command: CWD DKA4:[DKA4:[GENETIC_EPI_PATHVOL]
Response: 550-Failed to set default directory to
DKA4:[DKA4:[GENETIC_EPI_PATHVOL].
Response: 550 file specification syntax error
Error: Failed to retrieve directory listing}

[Alexander Schuch]

The syntax you used seem to be MVS syntax and no VMS syntax. You are aware of that?

[Tim Kosse]

Topic says MVS, describtion says VMS. Which is it?

[Alexander Schuch]

I changed "VMS" in the original bug summary to "MVS" as the syntax seems to be "MVS". As I
am not sure anymore, I changed it back and will let the original poster decide on it. :)

[gregglind]

Well, if that is MVS syntax (. for path seperators, [000000]
implying root) than it is MVS. In any case, the machine it
is hosted on is a VAX lingering in the company basement, and
I am no expert. In any case, the error still happens. I
seem to have probelems with recursive file upload into such
systems, when nested folders are involved. Should I file a
seperate report on it?

[Tim Kosse]

I think I've identified the bug. Please try tomorrow's
nightly (2006-11-07). Please reopen if this error did not
get fixed.