I am not sure about loading to a PDS, but if they are *.BIN files, should you use BINARY rather than ASCII as the type?
In the past when I have done something like this, I created a batch job to then create the PDS and load them. Usually IEBGENER - one member at a time Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Bill Ashton > Sent: Wednesday, August 05, 2015 6:45 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Problem with FTP into a PDS > > This group has been so helpful to me in the last couple weeks, and I hope for > one more victory! > > I am trying to download a group of fixes from our server into a PDS, to do > some reporting on it. I am not sure what my problem is, but let me explain > the commands I am using. > > CD the file server > LCD 'MY.PDS' > mget *.BIN (REPLACE > > This results in the following messages: > EZA1701I >>> TYPE A > 200 Type okay. > EZA1701I >>> PORT 141,202,65,11,170,236 > 200 PORT command successful. > EZA1701I >>> NLST *.BIN > 150 Opening ASCII mode data connection for /bin/ls. > 226 Listing completed. > EZA1701I >>> TYPE I > 200 Type okay. > EZA1685W Invalid local file identifier > EZA1735I Std Return Code = 22000, Error Code = 00018 > > I have confirmed that the files are on the server in the directory, and have > *.BIN as their mask. > > Could the problem be due to the server filename like ABCDEF.BIN and that > this can't create the desired member ABCDEF? Is there some other > command to tell FTP that my file is called ABCDEF.BIN, but store it locally as > ABCDEF in the PDS? > > Thanks once again! > Billy > > -- > Thank you and best regards, > *Billy Ashton* > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
