|
Yeah, i thought about it and wrote the string to a single record file. This logic works fine. Thanks for all your advices. Reddy. Kevin H <KevinH@kmtcinc.com>@midrange.com on 05/04/2001 07:25:30 AM Please respond to RPG400-L@midrange.com Sent by: owner-rpg400-l@midrange.com To: RPG400-L@midrange.com cc: Subject: Re: Interesting FTP question, URGENT That is what my testing implied, but I was not sure f that was a 400 limitation... to me the obvious way is to write the values to a 1 record file, and ftp the file... At 12:46 AM 5/4/2001, you wrote: >Hi Reddy, > >Is this something new? I thought the FTP PUT subcommand required a filename, >not a string of data to be sent. At least, that's what the manual claims. > >Curious, >Peter Dow >Dow Software Services, Inc. >909 425-0194 voice >909 425-0196 fax > >----- Original Message ----- >From: <RReddy@medicalartspress.com> >To: <RPG400-L@midrange.com> >Sent: Thursday, May 03, 2001 9:49 AM >Subject: Interesting FTP question, URGENT > > > > > > Hey Guys. > > > > I have a string of data ( length of data is 52) that i need to send to a > > server from AS400 through FTP. > > > > Now i might have all the 52 characters or i might have only 20 >characters > > but do remember i will always have the last 8 characters ( from location >45 > > - 52 ). > > > > The FTP process works fine if i have all the 52 characters but doesn't >work > > if i don't have all the 52 characters.. here is an example...when i try > > "put" statement....in my FTP process. > > > > put 20375817310010916180414010 0001RRE RRE.tmp > > > > The error message i get is > > > > "Number of arguments not valid for subcommand put." > > > > The error message make sense but is there a way i can work this process >out. > > > > Please advice > > Reddy > > > > > > +--- > > | This is the RPG/400 Mailing List! > > | To submit a new message, send your mail to RPG400-L@midrange.com. > > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: >david@midrange.com > > +--- > > >+--- >| This is the RPG/400 Mailing List! >| To submit a new message, send your mail to RPG400-L@midrange.com. >| To subscribe to this list send email to RPG400-L-SUB@midrange.com. >| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.