Default Remote Directory not working in v3.2.0 for MVS server type

[Steve Mann]

The Default Remote Directory for a MVS server type worked in v3.1.6 but not in v3.2.0. In v3.1.6 a directory of the form 'test' was accepted and was used correctly. In v3.2.0, the same value returns message "Default remote path cannot be parsed. Make sure it is valid and is supported by the slected server type.". v3.2.0 will accept values of the form /'test' or \'test' but neither value is used or saved.

[wesleydevrient]

I also came across this problem while connect to a MVS server. You can browse a folder by typing '\u' in the Remote site box after connecting (see attachment1.png). But if I want to set that as the Default remote directory I get the following error:
"Default remote path cannot be parsed. Make sure it is valid and is supported by the slected server type." (see attachment2.png)
I am also using FileZilla v3.2.0

[Tim Kosse]

Since when are slashes part of the MVS path syntax?

It's afaik all uppercase ASCII separated by dots and at the end maybe parenthesis for PDS members. All enclosed on single quotes.

'FOO.'
'FOO.BAR.'
'FOO.BAR(SOMETHING)'

[Steve Mann]

The Default Remote Directory for a MVS server type is still not working as of the nightly build for 02/18/2009.

[Tim Kosse]

See my previous reply.

[Steve Mann]

After a connection is made, the Remote Site path field will accept entries of the form

'FOO.'
'FOO.BAR.'
'FOO.BAR(SOMETHING)'

But these are not accepted in the Default Remote Directory field in Site Manager under the Advanced tab.

[Tim Kosse]

Ah, that is what you mean. The replies to this ticket made by wesleydevrient were more than confusing.

Will be fixed in 3.2.2