|
Ian, Do a DSPFFD on your source file and you'll see that there is more than just one field there. I suggest using FTP to a single field physical file and then copying from that file to your source file using CPYF with FMTOPT(*CVTSRC). Also, when you FTP the text file you will lose any characters that are past the record length. E.g. if your record length is 80 and your text file has a line with 85 characters on it, that line will be missing the last 5 characters. FTP does not line-wrap text files. Chuck ----- Original Message ----- From: "Ian J. Forsyth" <iforsyth@360GROUP.com> To: <MIDRANGE-L@midrange.com> Sent: Thursday, September 20, 2001 6:31 PM Subject: FTP Text File to Source File Member > I'm attempting to FTP SQL Source in a PC Text File to an iSeries Source File > Text Member. > Inside the Ftp Shell, I'm typing: > > ascii > put sqltext.txt mylib/qsrc.sqltext > > which transfers the file to the source member; however, when I inspect the > source member's data, I'm finding that there's a garbage character in front > of the first text character and blank spaces inserted between every > character in the file. In other words, if I transfer: > > TEXT > > I get in the source member: > > <garbage character>T E X T > > In some instances, the lines become really long and data gets truncated. > > If it makes a difference, I'm using notepad as my editor on the PC. Any > ideas on how to solve this one? > > Ian Forsyth > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.