|
They won't have records sizes. But do they have a record separator? Like CRLF? EDI has standard definitions and maybe there's a limit to the length of a particular piece of the packet. Just tried with a file first in PC record separation (CRLF), then UNIX style (LF only). As long as the count between separators is less than the physical's record length, you get individual records for each separator with FTP. If there are no separators, then you're left with going to the IFS, I think. Scott's idea of reading the IFS file directly has much merit, and can be done in RPG. It could simplify things a little, as you would not need to reconstruct things as I suspect you do now when it wraps. At 05:04 PM 4/23/02 -0400, you wrote: > From what I have been told they do not have record sizes defined for the >files on the Solaris system. The file length changes all the time because >it is EDI data. That is why if I bring it into the IFS I get all of the >file with out a defined size and when I do the CPYFRMSTMF it will wrap it >to whatever length the application needs it. In my case I need it in a 80 >record length file. > > > > >|---------+-----------------------------> >| | vhamberg@attbi.com| >| | Sent by: | >| | midrange-l-admin@m| >| | idrange.com | >| | | >| | | >| | 04/23/2002 12:29 | >| | PM | >| | Please respond to | >| | midrange-l | >| | | >|---------+-----------------------------> > > >>---------------------------------------------------------------------------------------------------------------------------------------------| > | > | > | To: midrange-l@midrange.com > | > | cc: > | > | Subject: RE: Copy from > IFS > | > > >>---------------------------------------------------------------------------------------------------------------------------------------------| > > > > > > >What is the longest record in the Solaris file? Is the record length of >your physical file that long? > >At 11:13 AM 4/23/02 -0400, you wrote: > > >If I FTP directly to the native file then some of the data is > >lost/truncated. The data is coming from a Solaris system. I tried to use > >the CRLF on the CPYFRMSTMF command but that does not wrap the data into >the > >file so anything over the 80th position is lost. > >Mike > > > > > > > > > > > >|---------+-----------------------------> > >| | mmanske@minter-wei| > >| | sman.com | > >| | Sent by: | > >| | midrange-l-admin@m| > >| | idrange.com | > >| | | > >| | | > >| | 04/23/2002 10:47 | > >| | AM | > >| | Please respond to | > >| | midrange-l | > >| | | > >|---------+-----------------------------> > > > > > >---------------------------------------------------------------------------------------------------------------------------------------------| > > > | > > | > > | To: midrange-l@midrange.com > > | > > | cc: > > | > > | Subject: RE: Copy from > > IFS > > | > > > > > >---------------------------------------------------------------------------------------------------------------------------------------------| > > > > > > > > > > > > > > >Just a couple of things, I have always just written the code to "skip" by > >the know > >records that have no data. > > > >The other thing, IMHO, sounds like extra work to me to have the ftp go to > >the ifs, > >and then have to get it to a flat "native" file; is there a reason you do > >not > >just ftp directly to a native iSeries/400 database file? > > > >HTH > >Mark > > > > > >-----Original Message----- > >From: midrange-l-admin@midrange.com > >[mailto:midrange-l-admin@midrange.com]On Behalf Of > >Mike.Windbeck@US.exel.com > >Sent: Tuesday, April 23, 2002 9:27 AM > >To: midrange-l@midrange.com > >Subject: Copy from IFS > > > > > >I am receiving a EDI data in a stream file via FTP into the IFS. After I > >receive the file I need to put that data into a flat file with an 80 >record > >length. I used the CPYFRMSTMF with *fixed as the end of line character. > >The data wraps correctly but I do not want the carriage-return and line > >feed. Is there any way to convert them to something else? I could write > >a preprocess program before the CPYFRMSTMF but was wondering what other > >ways this could be done. > >Thank you, > > > >Mike > > > > > > > > > >______________________________________________________________________ > >Important Email Information > > > >The information in this email is confidential and may be legally > >privileged. It is intended solely for the addressee. Access to this email > >by anyone else is unauthorized. If you are not the intended recipient, any > >disclosure, copying, distribution or any action taken or omitted to be > >taken in reliance on it, is prohibited and may be unlawful. If you are not > >the intended addressee please contact the sender and dispose of this > >e-mail. > > > >_______________________________________________ > >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. > > > > > >_______________________________________________ > >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. > > > > > > > > > > > >______________________________________________________________________ > >Important Email Information > > > > > > > >The information in this email is confidential and may be legally > >privileged. It is intended solely for the addressee. Access to this email > >by anyone else is unauthorized. If you are not the intended recipient, any > >disclosure, copying, distribution or any action taken or omitted to be > >taken in reliance on it, is prohibited and may be unlawful. If you are not > >the intended addressee please contact the sender and dispose of this > >e-mail. > > > > > >_______________________________________________ > >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. > >_______________________________________________ >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. > > > > > >______________________________________________________________________ >Important Email Information > > > >The information in this email is confidential and may be legally >privileged. It is intended solely for the addressee. Access to this email >by anyone else is unauthorized. If you are not the intended recipient, any >disclosure, copying, distribution or any action taken or omitted to be >taken in reliance on it, is prohibited and may be unlawful. If you are not >the intended addressee please contact the sender and dispose of this >e-mail. > > >_______________________________________________ >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-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.
midrange.com
