Re: eval-corr with record format as source -- RPG400-L

Subject: Re: eval-corr with record format as source
From: Lim Hock-Chai <Lim.Hock-Chai@xxxxxxxxxxxxxxx>
Date: Fri, 8 Feb 2013 20:27:21 +0000
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

I just couldn't think of any reason for not allowing record format as the source in eval-corr opcode. I can see why not to allow it in the target DS.

"Hockchai Lim" <lim.hock-chai@xxxxxxxxxxxxxxx> wrote in message news:<mailman.14513.1360331311.10847.rpg400-l@xxxxxxxxxxxx>...

It seems like eval-corr does not allow using record format name as the
source. I've a program where several fields in a record format have already
been defined as subfields in several different DS. So, using extname to
define this record format name and use it in eval-corr is not an option.
Other than eval one field at a time, Is there any other work around?

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.