× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



David,


It's Monday morning here (don't know about the rest of the world - yet) so maybe I am just not understanding the situation. So let me illustrate what I think I am hearing:

Input FILEA has fields:
FieldA
FieldB
FieldC

Output OUTA has fields:
OutA
OutB
OutC

Output OUTB has fields:
OutA
OutB
OutC

The program is doing something like:

OutA = FieldA
(etc.)
IF condition = 'A'
WRITE OUTAR
ELSE
WRITE OUTAR
WRITE OUTBR
ENDIF


The fact that OUTA and OUTB have the same field names would not make any difference. In fact, the OUT files could have the same field names as the input file (FILEA). Field names are just user-friendly references for memory address locations. But you knew that so my simple illustration is probably inaccurate; i.e., the problem is deeper than my little mud puddle.


* Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



David Foxwell wrote:
Hi,

I am reading a primary file with the RPG cycle
for each read, I write to one or both of my output files.

The fields of the second output file are also in the first.

How do I do this without having diffferent names and thus moving my data twice?


What I am doing at the moment, is writing to the first file and at LR I use SQL
to fill the second file from the first. But that way, I'm reading all the data
a second time.

Any ideas?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.