At least in my experience with Windows command line FTP there's a failure to parse the intermediate "dir" done by FTP before getting each member. I've seen this in other (GUI) FTP tools where the display of the PDS directory appears "wonky". It may work if your PDS has no ISPF or other data in the member information in the PDS directory. I've worked around this using Object Rexx, which is now free, open source and contains FTP functions. And there are some GUI FTP tools, the one which ships with IBM PCOMM for instance, which work correctly. Unsurprisingly you can do an mget from AIX, too. Last time I looked there's no RFC which describes exactly what the format of the response to DIR request is.
Regards, John Is there any kind of trace can be set on ftpd on why it just doesn't prompts me with a PDS member to download post the message 200 ? Strange it allows me to download other PDSes and only with one specific PDS it fails On Fri, 12 Jul, 2019, 5:39 PM Pommier, Rex,<rpomm...@sfgmembers.com> wrote:
John, Not sure what you mean here. If in ftp you do a "cd some.pds.name", you get a "some.pds.name is a partitioned dataset" message. You can then do a dir and get the PDS directory. You can also do an 'mget *' and it'll download the entire PDS, giving each member a separate file in your output directory. What sequence of commands causes bad behavior? Rex
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
