×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Sure, the prefixing is simpler, by far.  But if by chance you need to
update the contents of a record from one file with the contents of the
record from the other file, a single EVAL will  work, while with
prefixing, one eval per field is necessary.


On Thu, 30 Sep 2004 11:05:07 -0400, Dan Bale <dbale@xxxxxxxxxxxxx> wrote:
> In this scenario, I would definitely *consider* using the PREFIX keyword on
> the file specs as opposed to using the DS technique.
> 
> db
> 
> > -----Original Message-----
> > From: rpg400-l-bounces@xxxxxxxxxxxx / Tony Carolla
> > Sent: Thursday, September 30, 2004 10:37 AM
> >
> > Well, the only reason I have used them is a slightly broader-based
> > reason.  If you have two files, with the same record format, therefore
> > the same field names, and therefore the same buffers in your program,
> > sometimes you want to read a record from each file, and maintain the
> > two sets of data, for comparisons, or anything else.  READing,
> > CHAINing, etc. to a DS preserves the contents of the file buffer.  I
> > am certain there are more reasons that this.  Anybody?
> 
> --
> 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.
> 
> 



-- 
"Enter any 11-digit prime number to continue..."

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-2026 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.