Jump to content


SmartFTP and z/OS

This topic has been archived. This means that you cannot reply to this topic.
4 replies to this topic

#1 Sgibelli

  • Members
  • 9 posts

Posted 11 July 2003 - 06:51 AM

Hi all!

This is my first post. I have a some problems with SmartFTP (version
1.0.978) and an FTP server with z/OS (version 1.4 I think). The first little
problem is that the default switches for the LIST command (-a and -L) aren't supported (the execution of the commad results in a message like
this: "550 No data sets found."). I've resolved this disabling the switches
but a more serious problem occures. When I change to a new folder the
listing of the datasets doesn't appear or appears in a very reduced way
(only few datasets are shown) and with strange dates and dimensions.
This is an example:

PS PSGESTSS.SASPGM 0 byte 20/04/8000.

The same folder viewed with Windows 2000 command line FTP seems
to be good (obviously without attributes) and using the "Show raw listing"
command all informations (datasets and their attributes) are visible. I
know that z/OS isn't so widespread but I would like to know if this is a
limitation of SmartFTP (by the way, a fantastic FTP client :wink: ) or not.

Thanks a lot for any help.

#2 mb



  • Administrators
  • 11975 posts

Posted 14 July 2003 - 04:39 PM

Hello ..

Please send some raw listing and session logs to bugreport attttttttttt smartftp.com and we'll try to fix the problem(s).

Thank you.

#3 RSeery

  • Members
  • 1 posts

Posted 20 August 2003 - 04:35 PM

Any progress on this? I have the same symptoms. When I FTP to a OS/390 MVS system, everything works fine, but when I connect to the z/OS 1.4 system, the directory listing is wrong. I can sent raw list output if you want to see it......


#4 mb



  • Administrators
  • 11975 posts

Posted 20 August 2003 - 09:33 PM

No. Because we never got a listing.

Please send it to the email address above.


#5 mb



  • Administrators
  • 11975 posts

Posted 24 August 2003 - 10:19 PM

The bug should be fixed. It was a problem with the "UNIX"
string in the SYST reply message. But it should be fixed now:

Thanks for reporting.