Opened 11 years ago

Closed 11 years ago

#4908 closed Bug report (rejected)

z/os uss directory/file errors

Reported by: Steve Mann Owned by:
Priority: normal Component: FileZilla Client
Keywords: z/os uss Cc:
Component version: Operating system type: Other
Operating system version: Windows Vista 32bit

Description

Problems with FileZilla client 3.2.8.1 and z/OS USS directories and files. These happen with servertype set to "default(autodetect)" or "MVS, OS/390, z/OS" in SiteManager.

If I issue a change directory for USS in z/OS, the FileZilla changes the second or later / to a . in the directory name.

Command: CWD '/etc'
Response: 250 HFS directory /etc is the current working directory
Command: PWD
Response: 257 "/etc" is the HFS working directory.

Command: CWD msussl
Response: 250 HFS directory /etc/msussl is the current working directory
Command: PWD
Response: 257 "/etc/msussl" is the HFS working directory.

At this point I really am in directory /etc/msussl but it displays in FileZilla as /etc.msussl

File transfers are also being messed up. Sending a file to /etc/msussl should end as /etc/msussl/file but FileZilla is sending it as /etc.msussl(file).

Command: STOR '/etc.msussl(CA.der)'
Response: 125 Storing data set /etc.msussl(CA.der)
Response: 250 Transfer completed successfully.

Retrieving a file does this also. This should have been retrieving file /etc/msussl/CA.der

Command: RETR '/etc.msussl(CA.der)'
Response: 550 Command RETR fails: /etc.msussl(CA.der) does not exist.
Error: Critical error

Change History (1)

comment:1 by Tim Kosse, 11 years ago

Resolution: rejected
Status: newclosed

You cannot mix two different path syntaxes. If you use UNIX-style paths you need to keep using UNIX paths. If you're using MVS paths you need to always use MVS paths.

Note: See TracTickets for help on using tickets.