|
I surprised that FTP is overlooked as a file transmission tool in a lot of cases. All I hear is "Use PCTran" or some other obscure method. If you've got TCPIP, FTP is most likely your best bet in most cases.... I use it ALL the time... Especially since you can build scripts to run FTP jobs in batch, use the QUOTE command to execute commands, etc... Bradley V. Stone Taylor Corporation - OASIS Programmer/Analyst bvstone@taylorcorp.com > -----Original Message----- > From: Sannan Solberg [SMTP:SSolberg@Washcorp.com] > Sent: Thursday, December 10, 1998 4:00 PM > To: 'MIDRANGE-L@midrange.com' > Subject: RE: File Upload to 400-THANKS! > > I must have had a brain-fart or something. I thought I had tried FTP... > I > had tried uploading via a Rumba upload with a FDF and it hated it. FTP > worked like a dream directly into my file, just like I wanted! > > (snip) > > 1. CRTPF FILE(ANYFILE) RCDLEN(60) on the AS400. > > 2. FTP the text file into ANYFILE. > > > > -----Original Message----- > > From: Sannan Solberg [mailto:SSolberg@Washcorp.com] > > Sent: Thursday, December 10, 1998 9:16 AM > > To: 'MIDRANGE-L@midrange.com' > > Subject: File Upload to 400 > > > > I have a file on my PC that is simple text file but the > > vendor neglected to > > put end-of-record markers at the end of each (60 char) > > record. Each field > > in the record is fixed length and starting column, ie. no > > delimiters. I've > > tried a few things such as uploading through a file > > description on the PC of > > the physical, and it hated that there was no marker. I > > uploaded the file > > into a document folder and tried CPYFRMPCD into 60 char flat > > physical (no > > fields) and it didn't like that either. I even tried using > > the most recent > > posts regarding CPYFRMINPF and didn't seem to get anywhere > > (it also didn't > > lilke anything I gave it). Any ideas??? (TIA) I am > > avoiding having to > > massage the file on the PC at all costs. > > > > > +--- > > > | This is the Midrange System Mailing List! > > > | To submit a new message, send your mail to > > MIDRANGE-L@midrange.com. > > > | To subscribe to this list send email to > > MIDRANGE-L-SUB@midrange.com. > > > | To unsubscribe from this list send email to > > MIDRANGE-L-UNSUB@midrange.com. > > > | Questions should be directed to the list owner/operator: > > david@midrange.com > > > +--- > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.