Client does not show all files from z/OS

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
robi
500 Command not understood
Posts: 1
Joined: 2020-02-24 08:30

Client does not show all files from z/OS

#1 Post by robi » 2020-02-24 10:05

Hello

I found a strange behaviour in the client connected to a z/OS server.
Not all files are displayed. In z/OS there is the parameter LISTSERV which controls how to display the filesize.
If LISTSERV=1 the FTP server shows very large files with +++++ in the size. These lines are not displayed in the filezilla client.
See the filezilla log:

Code: Select all

Command:	site listlevel=1
Response:	200 SITE command was accepted
Status:	Retrieving directory listing of "'PRDPR.WAS.P2.ERROR.LOG.'"...
Command:	CWD 'PRDPR.WAS.P2.ERROR.LOG.'
Response:	250 "PRDPR.WAS.P2.ERROR.LOG." is the working directory name prefix.
Command:	PWD
Response:	257 "'PRDPR.WAS.P2.ERROR.LOG.'" is working directory.
Command:	TYPE I
Response:	200 Representation type is Image
Command:	PASV
Response:	227 Entering Passive Mode (172,30,3,14,220,134)
Trace:	Binding data connection source IP to control connection source IP 10.4.7.50
Command:	LIST
Response:	125 List started OK
Listing:	Volume Unit    Referred Ext Used Recfm Lrecl BlkSz Dsorg Dsname
Listing:	VSAM A0002428
Listing:	PM3C39 3390                                        VSAM A0002428.DATA
Listing:	VSAM A0002449
Listing:	PM3C53 3390                                        VSAM A0002449.DATA
Listing:	VSAM A0002450
Listing:	PM3C4C 3390                                        VSAM A0002450.DATA
Listing:	VSAM A0002451
Listing:	PM3C31 3390                                        VSAM A0002451.DATA
Listing:	VSAM A0002452
Listing:	PM3C36 3390                                        VSAM A0002452.DATA
Listing:	VSAM A0002453
Listing:	PM3C29 3390                                        VSAM A0002453.DATA
Listing:	VSAM A0002454
Listing:	PM3C33 3390                                        VSAM A0002454.DATA
Listing:	VSAM A0002455
Listing:	PM3C21 3390                                        VSAM A0002455.DATA
Listing:	VSAM A0002456
Listing:	PM3C23 3390                                        VSAM A0002456.DATA
Listing:	VSAM A0002457
Listing:	PM3C26 3390                                        VSAM A0002457.DATA
Listing:	VSAM A0002458
Listing:	PM3C52 3390                                        VSAM A0002458.DATA
Listing:	PM3C60 3390   2019/10/28  379440  VB   32756 32760  PS  D191019.D191026.TXT
Listing:	PM3C2F 3390   2019/11/04  280130  VB   32756 32760  PS  D191026.D191102.TXT
Listing:	PM37C6 3390   2019/11/11  387015  VB   32756 32760  PS  D191102.D191109.TXT
Listing:	PM3C6A 3390   2019/12/12  5+++++  VB   32756 32760  PS  D191109.D191116.TXT
Listing:	PM3C29 3390   2019/11/25  4+++++  VB   32756 32760  PS  D191116.D191123.TXT
Listing:	PM3C32 3390   2019/12/02  4+++++  VB   32756 32760  PS  D191123.D191130.TXT
Listing:	PM3C60 3390   2019/12/09  8+++++  VB   32756 32760  PS  D191130.D191207.TXT
Listing:	PM3C42 3390   2019/12/16  3+++++  VB   32756 32760  PS  D191207.D191214.TXT
Listing:	PM3C35 3390   2019/12/30  3+++++  VB   32756 32760  PS  D191214.D191221.TXT
Listing:	PM3C20 3390   2020/01/17  162490  VB   32756 32760  PS  D191221.D191228.TXT
Listing:	PM3C30 3390   2020/01/17  273755  VB   32756 32760  PS  D191228.D200104.TXT
Listing:	PM3C23 3390   2020/01/13  2+++++  VB   32756 32760  PS  D200104.D200111.TXT
Listing:	PM3C3E 3390   2020/01/20  2+++++  VB   32756 32760  PS  D200111.D200118.TXT
Listing:	PM3C2D 3390   2020/01/31  2+++++  VB   32756 32760  PS  D200118.D200125.TXT
Listing:	PM3C41 3390   2020/02/03  296150  VB   32756 32760  PS  D200125.D200201.TXT
Listing:	PM3C2A 3390   2020/02/10  4+++++  VB   32756 32760  PS  D200201.D200208.TXT
Listing:	PM3C55 3390   2020/02/17  4+++++  VB   32756 32760  PS  D200208.D200215.TXT
Listing:	PM3C21 3390   2020/02/24  125710  VB   32756 32760  PS  D200215.D200222.TXT
Listing:	PM3C5F 3390   2020/01/17  1   45  VB   32756 32760  PS  FILTERED.TXT
Listing:	PM3C40 3390   2020/02/23  138355  VB   32756 32760  PS  LISTING
Listing:	VSAM WEB3
Listing:	PM3C25 3390                                        VSAM WEB3.DATA
Listing:	VSAM WEB4
Listing:	PM3C35 3390                                        VSAM WEB4.DATA
Listing:	VSAM WEB5
Listing:	PM3C51 3390                                        VSAM WEB5.DATA
Listing:	VSAM WEB6
Listing:	PM3C27 3390                                        VSAM WEB6.DATA
Response:	250 List completed successfully.
Status:	Directory listing of "'PRDPR.WAS.P2.ERROR.LOG.'" successful
FileZilla_LISTSERV1.png
FileZilla_LISTSERV1.png (152.82 KiB) Viewed 3593 times
If LISTSERV=2 the FTP server enlarges the field for the filesize. But in this case the filezilla client does not show any file anymore.

Code: Select all

Command:	site listlevel=2
Response:	200 SITE command was accepted
Status:	Retrieving directory listing of "'PRDPR.WAS.P2.ERROR.LOG.'"...
Command:	CWD 'PRDPR.WAS.P2.ERROR.LOG.'
Response:	250 "PRDPR.WAS.P2.ERROR.LOG." is the working directory name prefix.
Command:	PWD
Response:	257 "'PRDPR.WAS.P2.ERROR.LOG.'" is working directory.
Command:	TYPE I
Response:	200 Representation type is Image
Command:	PASV
Response:	227 Entering Passive Mode (172,30,3,14,176,0)
Trace:	Binding data connection source IP to control connection source IP 10.4.7.50
Command:	LIST
Response:	125 List started OK
Listing:	Volume Referred      Ext      Used Recfm Lrecl BlkSz Dsorg Dsname
Listing:	VSAM  A0002428
Listing:	PM3C39                                               VSAM  A0002428.DATA
Listing:	VSAM  A0002449
Listing:	PM3C53                                               VSAM  A0002449.DATA
Listing:	VSAM  A0002450
Listing:	PM3C4C                                               VSAM  A0002450.DATA
Listing:	VSAM  A0002451
Listing:	PM3C31                                               VSAM  A0002451.DATA
Listing:	VSAM  A0002452
Listing:	PM3C36                                               VSAM  A0002452.DATA
Listing:	VSAM  A0002453
Listing:	PM3C29                                               VSAM  A0002453.DATA
Listing:	VSAM  A0002454
Listing:	PM3C33                                               VSAM  A0002454.DATA
Listing:	VSAM  A0002455
Listing:	PM3C21                                               VSAM  A0002455.DATA
Listing:	VSAM  A0002456
Listing:	PM3C23                                               VSAM  A0002456.DATA
Listing:	VSAM  A0002457
Listing:	PM3C26                                               VSAM  A0002457.DATA
Listing:	VSAM  A0002458
Listing:	PM3C52                                               VSAM  A0002458.DATA
Listing:	PM3C60 2019/10/28      3     79440  VB   32756 32760  PS   D191019.D191026.TXT
Listing:	PM3C2F 2019/11/04      2     80130  VB   32756 32760  PS   D191026.D191102.TXT
Listing:	PM37C6 2019/11/11      3     87015  VB   32756 32760  PS   D191102.D191109.TXT
Listing:	PM3C6A 2019/12/12      5    159795  VB   32756 32760  PS   D191109.D191116.TXT
Listing:	PM3C29 2019/11/25      4    202875  VB   32756 32760  PS   D191116.D191123.TXT
Listing:	PM3C32 2019/12/02      4    135000  VB   32756 32760  PS   D191123.D191130.TXT
Listing:	PM3C60 2019/12/09      8    135000  VB   32756 32760  PS   D191130.D191207.TXT
Listing:	PM3C42 2019/12/16      3    135000  VB   32756 32760  PS   D191207.D191214.TXT
Listing:	PM3C35 2019/12/30      3    190425  VB   32756 32760  PS   D191214.D191221.TXT
Listing:	PM3C20 2020/01/17      1     62490  VB   32756 32760  PS   D191221.D191228.TXT
Listing:	PM3C30 2020/01/17      2     73755  VB   32756 32760  PS   D191228.D200104.TXT
Listing:	PM3C23 2020/01/13      2    103005  VB   32756 32760  PS   D200104.D200111.TXT
Listing:	PM3C3E 2020/01/20      2    114135  VB   32756 32760  PS   D200111.D200118.TXT
Listing:	PM3C2D 2020/01/31      2    105450  VB   32756 32760  PS   D200118.D200125.TXT
Listing:	PM3C41 2020/02/03      2     96150  VB   32756 32760  PS   D200125.D200201.TXT
Listing:	PM3C2A 2020/02/10      4    231900  VB   32756 32760  PS   D200201.D200208.TXT
Listing:	PM3C55 2020/02/17      4    144645  VB   32756 32760  PS   D200208.D200215.TXT
Listing:	PM3C21 2020/02/24      1     25710  VB   32756 32760  PS   D200215.D200222.TXT
Listing:	PM3C5F 2020/01/17      1        45  VB   32756 32760  PS   FILTERED.TXT
Listing:	PM3C40 2020/02/23      1     38355  VB   32756 32760  PS   LISTING
Listing:	VSAM  WEB3
Listing:	PM3C25                                               VSAM  WEB3.DATA
Listing:	VSAM  WEB4
Listing:	PM3C35                                               VSAM  WEB4.DATA
Listing:	VSAM  WEB5
Listing:	PM3C51                                               VSAM  WEB5.DATA
Listing:	VSAM  WEB6
Listing:	PM3C27                                               VSAM  WEB6.DATA
Response:	250 List completed successfully.
Status:	Directory listing of "'PRDPR.WAS.P2.ERROR.LOG.'" successful
FileZilla_LISTSERV2.png
FileZilla_LISTSERV2.png (134.87 KiB) Viewed 3593 times
I run filezilla 3.46.3. Is this a bug, or is there a setting to get all files displayed?

User avatar
botg
Site Admin
Posts: 35492
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Client does not show all files from z/OS

#2 Post by botg » 2020-02-24 12:46

This is a won't-fix. You need to update to a more modern FTP server software that implements MLSD (and ideally also TVFS) from RFC 3659.

tkroller25
500 Command not understood
Posts: 2
Joined: 2022-09-12 13:46
First name: Terry
Last name: Roller

Re: Client does not show all files from z/OS

#3 Post by tkroller25 » 2022-09-12 14:12

I'd like to revisit this if I may. In a different forum thread (viewtopic.php?t=7237), you stated:
"A proper server should not support "LIST -a" and should not hide any files from the user ever."

While the "LIST -a" part is not relevant, the latter portion of the statement is exactly what is happening here.
FileZilla is hiding files from the user. We see the files in the FileZilla log exactly as the original poster explained, yet FileZilla is not including them.
We have not found any setting that will cause FileZilla to display those files even though they are being returned from the server.

Thank you,

Terry Roller
FileZilla 3.60.2

User avatar
botg
Site Admin
Posts: 35492
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Client does not show all files from z/OS

#4 Post by botg » 2022-09-12 14:40

This has nothing to do with LIST -a.

User avatar
boco
Contributor
Posts: 26899
Joined: 2006-05-01 03:28
Location: Germany

Re: Client does not show all files from z/OS

#5 Post by boco » 2022-09-12 17:56

Your analogy is flawed. First, @botg spoke about servers, not clients. Second, as LIST output has never been standardized, there are infinity+1 ways for a server to format the output. FileZilla supports the most common ones but cannot do for all, more so as there are well standardized listing commands available (MLSD). In other words, your server simply doesn't send the listing in any format FileZilla can understand and parse. That's nothing to do with "hiding files".
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Please do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

tkroller25
500 Command not understood
Posts: 2
Joined: 2022-09-12 13:46
First name: Terry
Last name: Roller

Re: Client does not show all files from z/OS

#6 Post by tkroller25 » 2022-09-19 14:09

I am referring to the log that FileZilla provides showing the exact response from the server.
The format of the files returned by the server is identical for files being included by FileZilla and files being excluded by FileZilla. The difference is that if the size exceeds 99999, the server result shows "+++++" for the size. Those are the ones being excluded.

So, this leads me to this question....Is it necessary for FileZilla to be aware of the file size for it to include the file in the results? Honest question, because I do not know.

Terry

User avatar
botg
Site Admin
Posts: 35492
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Client does not show all files from z/OS

#7 Post by botg » 2022-09-19 14:24

With a machine-readable format, such as the out put of MLSD, size can be optional.

With non-machine-readable formats, there are so many possible variations and deviations that it is not possible to support all human-readable flavors, especially due to mutually exclusive ambiguities.

Just update to a modern server supporting MLSD, it's as simple as that.

Post Reply