|
Thanks for the suggestion. I'll have to look into that further. -----Original Message----- From: Scott Klement [mailto:klemscot@xxxxxxxxxxxx] Sent: Monday, January 12, 2004 2:29 PM To: RPG programming on the AS400 / iSeries Subject: RE: Copying to a Stream File Rather than write your data to a database file with fixed-length records, and then try to get that file to somehow convert to the format that you want, I recommend just writing it in the correct format in the first place. In other words, skip the database file and write directly to a stream file. I've got a tutorial on-line which explains how to work with the IFS from an RPG program. You can read it here: http://www.scottklement.com/rpg/ifs.html On Mon, 12 Jan 2004, Kara Ketcham wrote: > > I am trying to copy a physical file to a stream file that will be > imported into another system. This other system cannot accept carriage > returns or line feeds so I have created a physical file with one field > that is defined as 80 characters long. The data is formatted so that it > is written out to this file as one long string with a '~' separating > each segment. The problem is that when the last record is written out, > it does not fill the entire 80 characters of the field. I can not have > anything after the last '~' - no carriage return, no line feed, no eof > terminator, and not even blanks. Does anyone have a suggestion? > _______________________________________________ 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.
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.