RE: Comments in an FTP input script

First an update, then a question for Booth

I tried just putting comments into the ftp input script and letting it
'error out' and this is what I found - and it was very surprising!

i tried something like this:

##  loc=290f  date=20020825   type=S  tname=SLS20020825

and in the output log, I got this back:

> ##  ********  *************   ******  *****************
Subcommand '##' not valid.

!!! it had replaced my data with asterisks!   maybe to hide a failed
attempt at user and password entry?  that was wierd.

I tried several other things, and the only thing that worked was:

#loc=290f
#date=20020825
#type=S
#tname=SLS20020825

i.e. on separate lines.   it seems that it will only return the first word
of each line in an error situation.

this quadruples my errors, but it still runs very fast.  I wonder if FTP
has an error threshhold?  i guess we'll see. ;)


Booth,  where do I find the FTP log, and how is it different from the
output log provided by ovrdbf output sourcfile?

Thanks,

Rick

----original message--------
In a similar situation I've relied upon the log file.  This can be created,
saved, and read easily on the AS/400 green-screen.  The client's
understanding of the log file is more probable than any other solution that
is reasonable to expect.  Couple that with a program to allow the script
file(s) to be edited by their staff, and your problem should at least be
manageable and within the the ordinary CL and RPGLE

I've done a FTP scripting thing.  It may be a little more than you want,
but
e-mail me if you'd like to peek at the code.

---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@MartinVT.com
---------------------------------------------------------