Re: writing ifs file-odd specs

website. I've worked in and around the IFS for years, but your IFSeBook was
very clear and easy to follow, and a tremendous help.
Jim Franz

To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Sunday, January 22, 2006 8:49 PM
Subject: RE: writing ifs file-odd specs

Normally FTP tells the other side how many bytes are being sent.

No, sorry... that simply isn't true.  FTP may send a human-readable
informational message that says how big the file is, but that is totally
optional, the server can say anything it likes in that message, it's
totally free form,and the number of bytes is totually optional and not
used by the FTP protocol for any reason.

The end of a file in FTP is detected by the sending of a "226 Transfer
Complete" message on the control channel.  If that message is received,
the receiver knows that all of the data was sent and the data channel is
closed.

I agree that whether or not you have CRLF at the end of the file won't
have any effect on FTP, however, I do not agree with your statement that
the number of bytes sent has any impact on it.

I suspect the requirement means a CRLF is optional on the final record in

the file, but required between all other records in the file. Why? Because once the file transfer is complete, the receiving program can infer whatever

it wants, including a CRLF.

Yes... or to put it another way: If it receives an "End of File" error,
the program will know that it's also at the end of the record.  After all,
when the file is done, the record must also be done.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.