|
These are the ways I'd try to deal with this file, in order of how I prefer them... If you can't use one, move on to the next. 1) Read the stream file directly in the program that needs the data. 2) FTP directly to a PF, skip the stream file. 3) Try CPYFRMIMPF to convert stream file to PF. 4) Try CPYFRMSTMF to convert stream file to PF. 5) Write a program to convert stream file to PF. If you have the ability to change the program, option #1 should always work, and it's the most intuitive way to do it, since you're not moving it from file to file, with chance for errors at each step. Options 2-4 are the quickest and easiest to implement, but are limited in what they can do. Option #5 is a compromise -- and should always work, as long as you're willing & able to do the programming. On Tue, 23 Apr 2002 Mike.Windbeck@US.exel.com 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. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.